Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improving testing of release process #2059

Open
tim-schilling opened this issue Jan 18, 2025 · 2 comments
Open

Improving testing of release process #2059

tim-schilling opened this issue Jan 18, 2025 · 2 comments

Comments

@tim-schilling
Copy link
Member

I propose we allow suffixing the version number from an environment variable. This would then be utilized in our test release process to build the package with a unique version number.

The new action would run on the following events:

  • A tag is pushed (same as today)
  • Once a month
  • A workflow_dispatch with a unique iteration value

There is more information on how this would be implemented here: https://github.com/django-commons/best-practices/blob/main/docs/releases.md

@devatbosch
Copy link

Hi @tim-schilling , I would like to work on this issue if none are working on it.
If so Could you plz hint me on the end-result/expectation to fix this issue...

@tim-schilling
Copy link
Member Author

Hi @devatbosch, this is currently under discussion, so I'm not sure we'll implement anything for it.

However, if we do, I suspect the solution will be similar to https://github.com/django-commons/best-practices/blob/main/docs/releases.md#testing-releases and how that repo does it. Check the pyproject.toml file, the project's topmost __init__.py file and the test_release.yml GitHub action.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants