Developmental releases on demand #2190
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
ognyanstoimenov
changed the title
poodlewars
approved these changes
Feb 20, 2025
jamesmunro
pushed a commit
that referenced
this pull request
Feb 25, 2025
#### Reference Issues/PRs <!--Example: Fixes #1234. See also #3456.--> * New workflow that on trigger creates a dev release from current master * Calculates what next version would be and names the release `x.y.z.dev0+<master_sha>` * Release scripts introduced in #2174 had some permissions/token issues. This fixes them. * Not working (5.2.4 branch, check annotations); https://github.com/man-group/ArcticDB/actions/runs/13397301934 https://github.com/man-group/ArcticDB/actions/runs/13409868194 * Working (5.2.4 after applying this): * https://github.com/man-group/ArcticDB/actions/runs/13410089783 #### What does this implement or fix? ## Change Type (Required) - [x] **Patch** (Bug fix or non-breaking improvement) - [ ] **Minor** (New feature, but backward compatible) - [ ] **Major** (Breaking changes) - [ ] **Cherry pick** #### Any other comments? #### Checklist <details> <summary> Checklist for code changes... </summary> - [ ] Have you updated the relevant docstrings, documentation and copyright notice? - [ ] Is this contribution tested against [all ArcticDB's features](../docs/mkdocs/docs/technical/contributing.md)? - [ ] Do all exceptions introduced raise appropriate [error messages](https://docs.arcticdb.io/error_messages/)? - [ ] Are API changes highlighted in the PR description? - [ ] Is the PR labelled as enhancement or bug so it appears in autogenerated release notes? </details> <!-- Thanks for contributing a Pull Request to ArcticDB! Please ensure you have taken a look at: - ArcticDB's Code of Conduct: https://github.com/man-group/ArcticDB/blob/master/CODE_OF_CONDUCT.md - ArcticDB's Contribution Licensing: https://github.com/man-group/ArcticDB/blob/master/docs/mkdocs/docs/technical/contributing.md#contribution-licensing -->
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.
Reference Issues/PRs
New workflow that on trigger creates a dev release from current master
x.y.z.dev0+<master_sha>Release scripts introduced in Automated Release scripts #2174 had some permissions/token issues. This fixes them.
Not working (5.2.4 branch, check annotations);
https://github.com/man-group/ArcticDB/actions/runs/13397301934
https://github.com/man-group/ArcticDB/actions/runs/13409868194
Working (5.2.4 after applying this):
https://github.com/man-group/ArcticDB/actions/runs/13410089783
What does this implement or fix?
Change Type (Required)
Any other comments?
Checklist
Checklist for code changes...