Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Running `github-release` only for the most recent release
See original GitHub issueThe docs for the scriv github-release command imply that it will create/update releases for every version documented in the CHANGELOG, which I suspect will lead to problems in our case. Is there a way to only create/edit the most recent/topmost release in the CHANGELOG?
Issue Analytics
- State:
- Created a year ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Managing releases in a repository - GitHub Docs
Creating a release · On GitHub.com, navigate to the main page of the repository. · To the right of the list of files,...
Read more >Automatic Releases · Actions · GitHub Marketplace
Automate the GitHub release process with assets, changelogs, pre-releases, and more.
Read more >Releases - GitHub Docs
View the latest published full release for the repository. The latest release is the most recent non-prerelease, non-draft release, sorted by the created_at ......
Read more >release-it/release-it: Automate versioning and ... - GitHub
Use release-it for version management and publish to anywhere with its versatile configuration, a powerful plugin system, and hooks to execute any command...
Read more >GitHub Releases for Automated Package Publishing · Actions
There are several ways to do automated releases and package publishing via GitHub actions, but many of them have drawbacks, at least in...
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
Honestly it might make more sense for the default to be only the latest release, and have an option to consider all the releases. I think that will line up best with people’s expectations and workflow, and will make adoption easiest. It will be a breaking change, but we are still <1.0.
THANK YOU!