Automatic package release should start from the state of the repo that was reviewed
See original GitHub issueas discussed in #144, there is a risk that the diff being reviewed in the PR that bumps the package version no longer match the state of the repo when that PR is merged.
The GH action that does the release should start from the state of the repo at the time of the diff.
We could for instance tag the repo as pre-x.y.z when generating the diff, and use that tag for the checkout in the release action.
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (7 by maintainers)
Top Results From Across the Web
Repo Command Reference | Android Open Source Project
Installs Repo in the current directory. This creates a .repo/ directory with Git repositories for the Repo source code and the standard Android ......
Read more >Repository checks - GitLab Documentation
Manually trigger this check for a project, using the GitLab UI. Schedule this check to run automatically for all projects. Run this check...
Read more >Git branch policies and settings - Azure Repos - Microsoft Learn
To manage branch policies, select Repos > Branches to open the Branches page in the web portal. Screenshot that shows the Branches menu...
Read more >Chapter 21 Git Version Control | Bioconductor Packages
During the review process you will likely need to update your package. Do this in your local repository by first making sure your...
Read more >GitHub Integration (Heroku GitHub Deploys)
After you link your Heroku app to a GitHub repo, ... When enabled, Heroku will only auto-deploy after all the commit statuses of...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

It’s below
that rule"Require status checks to pass before merging", if you check it then it will appear.One remaining bug tracked in #244, and a few possible improvements tracked in #226, #232, #237 but new workflows are now in place and documented in the README. New workflows guarantee that the package released is the package that was reviewed.
Closing this issue accordingly.