Skip to content

chore: prepare release v0.14.0-alpha.1#1743

Merged
mmagician merged 12 commits intonextfrom
mmagician-use-storage-map-key-wrapper
Mar 4, 2026
Merged

chore: prepare release v0.14.0-alpha.1#1743
mmagician merged 12 commits intonextfrom
mmagician-use-storage-map-key-wrapper

Conversation

@mmagician
Copy link
Contributor

  • bump workspace and dependency versions to v0.14.0-alpha.1
  • adapt the CI job to release from other branch than just main (in particular, after merging this to next, we'll branch off to a new release/v0.14.0-alpha from which the alpha release will be triggered
  • protocol introduced a new StorageMapEntry (& StorageMapKeyHash) wrapper around Word, which required a few changes to migrate to that new interface

claude and others added 6 commits March 3, 2026 09:52
Pin protocol dependencies to published crate versions and update all
workspace crate versions to =0.14.0-alpha.1.

https://claude.ai/code/session_017j1F8cwRXFnWyjzzwN9d4k
Use github.event.release.target_commitish to dynamically determine
which branch to checkout and verify against, instead of hardcoding
main. This enables releasing alpha versions from the next branch.

https://claude.ai/code/session_017j1F8cwRXFnWyjzzwN9d4k
@mmagician mmagician added the no changelog This PR does not require an entry in the `CHANGELOG.md` file label Mar 3, 2026
@mmagician mmagician force-pushed the mmagician-use-storage-map-key-wrapper branch from dc28c6c to e9ceef3 Compare March 3, 2026 20:48
Comment on lines +25 to +26
# checked out.
- name: Verify release was triggered from release branch HEAD
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't this always true now? The check can probably just be yanked?

Copy link
Contributor Author

@mmagician mmagician Mar 4, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it was not strictly always true (e.g. when the release was triggered from a branch, but then a new commit was pushed to that branch before this step run).

However, while at it, I figured out that this was probably overcomplicating things too much overall. I changed the workflow to always check out the tag that the release came from (disregarding commit SHAs and branch names altogether). I think this is cleaner overall, WDYT @Mirko-von-Leipzig?

7e5d1a8


I also brought in the MSVR script which was only on main

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can always iterate on this if needed

@mmagician mmagician requested a review from drahnr March 4, 2026 14:36
@mmagician mmagician merged commit f6afa69 into next Mar 4, 2026
18 checks passed
@mmagician mmagician deleted the mmagician-use-storage-map-key-wrapper branch March 4, 2026 15:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no changelog This PR does not require an entry in the `CHANGELOG.md` file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants