Mechanized Release Process #380
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Nicolas Braud-Santoni <nicolas@braud-santoni.eu>
Co-authored-by: Nicolas Braud-Santoni <nicolas@braud-santoni.eu>
Need the `git` command with setuptools_scm Co-authored-by: Nicolas Braud-Santoni <nicolas@braud-santoni.eu>
|
Note that I don't really expect this to be merged. It's more along the lines of "demo then discuss". |
Can't easily install git into the windows container, so just use the built wheel Co-authored-by: Nicolas Braud-Santoni <nicolas@braud-santoni.eu>
AstraLuma
force-pushed
the
ci-auto-release
branch
from
7a12fad
to
feb2353
Compare
Co-authored-by: Nicolas Braud-Santoni <nicolas@braud-santoni.eu>
AstraLuma
force-pushed
the
ci-auto-release
branch
from
2fd8e75
to
2dadc9e
Compare
Co-authored-by: Nicolas Braud-Santoni <nicolas@braud-santoni.eu>
|
Ok, I'm going to leave the shuffling of artifacts around until we decide to actually do this. |
Alright this is pretty much the thing that settles my doubts. It gives us a live preview of the build artifacts before we cut a release. If you and @nbraud are happy with this, I'm happy with it. |
Co-authored-by: Nicolas Braud-Santoni <nicolas@braud-santoni.eu>
AstraLuma
force-pushed
the
ci-auto-release
branch
from
7d9d3d3
to
e2a1f56
Compare
Co-authored-by: Nicolas Braud-Santoni <nicolas@braud-santoni.eu>
Co-authored-by: Nicolas Braud-Santoni <nicolas@braud-santoni.eu>
Co-authored-by: Nicolas Braud-Santoni <nicolas@braud-santoni.eu>
Co-authored-by: Nicolas Braud-Santoni <nicolas@braud-santoni.eu>
AstraLuma
force-pushed
the
ci-auto-release
branch
from
335a1e3
to
324de9e
Compare
|
Ok, CI is green. Just need to add the API tokens, and this should be good. |
|
NVM. I can't log in as the bot because of Security:tm:, so the credentials will have to wait. |
Co-authored-by: Nicolas Braud-Santoni <nicolas@braud-santoni.eu>
This reverts commit 35569d4.
Co-authored-by: Nicolas Braud-Santoni <nicolas@braud-santoni.eu>
|
Tokens are in place. Tested uploads. I think this is good. |
|
Off we go into the new world. bors r+ |
bors bot
added a commit
that referenced
this pull request
Feb 20, 2020
380: Mechanized Release Process r=pathunstrom a=astronouth7303 Implements a mechanized release process. Under this, the release process would be: 1. Go to GitHub Release pages 2. Look at the diff since last version, compile changelog 3. On the GitHub site, create a tag/release with the changelog and any other release notes 4. Cirrus CI is responsible for building and uploading to PyPI and GitHub Additionally, dev releases are uploaded to PyPI test every time `master` is updated. Version numbers are no longer explicitly listed in the repo, instead being calculated based on the git tags. This code is a pretty direct copy from https://github.com/gqlmod/gqlmod (which is in part based on code that @duckinator wrote). @nbraud originally proposed this for PPB. Co-authored-by: Jamie Bliss <jamie@ivyleav.es>
Timed out |
|
bors retry |
bors bot
added a commit
that referenced
this pull request
Feb 20, 2020
380: Mechanized Release Process r=pathunstrom a=astronouth7303 Implements a mechanized release process. Under this, the release process would be: 1. Go to GitHub Release pages 2. Look at the diff since last version, compile changelog 3. On the GitHub site, create a tag/release with the changelog and any other release notes 4. Cirrus CI is responsible for building and uploading to PyPI and GitHub Additionally, dev releases are uploaded to PyPI test every time `master` is updated. Version numbers are no longer explicitly listed in the repo, instead being calculated based on the git tags. This code is a pretty direct copy from https://github.com/gqlmod/gqlmod (which is in part based on code that @duckinator wrote). @nbraud originally proposed this for PPB. Co-authored-by: Jamie Bliss <jamie@ivyleav.es>
Canceled |
|
bors retry |
Build succeeded
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implements a mechanized release process. Under this, the release process would be:
Additionally, dev releases are uploaded to PyPI test every time
masteris updated.Version numbers are no longer explicitly listed in the repo, instead being calculated based on the git tags.
This code is a pretty direct copy from https://github.com/gqlmod/gqlmod (which is in part based on code that @duckinator wrote).
@nbraud originally proposed this for PPB.