ci: configure shared UI v2 alpha releases - #57
Merged
uermel merged 1 commit intoAug 18, 2026
Conversation
uermel
force-pushed
the
uermel/zarr-v3-final-alpha-release
branch
from
August 18, 2026 17:40
47f38d3 to
5c253c9
Compare
uermel
force-pushed
the
uermel/zarr-v3-final-alpha-release
branch
from
August 18, 2026 17:43
5c253c9 to
85b9458
Compare
uermel
force-pushed
the
uermel/zarr-v3-final-alpha-release
branch
from
August 18, 2026 20:59
85b9458 to
49a0906
Compare
Release-As: 2.0.0-alpha.1
uermel
force-pushed
the
uermel/zarr-v3-final-alpha-release
branch
from
August 18, 2026 21:10
49a0906 to
2d941cd
Compare
uermel
pushed a commit
that referenced
this pull request
Aug 18, 2026
🤖 I have created a release *beep* *boop* --- ## [2.0.0-alpha.1](copick-shared-ui-v0.7.0...copick-shared-ui-v2.0.0-alpha.1) (2026-08-18) ### ⚠ BREAKING CHANGES * adopt metadata-driven Zarr 3 thumbnails ([#55](#55)) ### ✨ Features * adopt metadata-driven Zarr 3 thumbnails ([#55](#55)) ([a02ecfb](a02ecfb)) ### 🧪 Tests * establish shared UI migration gate ([#54](#54)) ([73b6f74](73b6f74)) * validate migrated thumbnail backends ([#56](#56)) ([72f94a7](72f94a7)) ### ⚙ Continuous Integration * bootstrap shared UI v2 alpha version ([a73b9c4](a73b9c4)) * configure shared UI v2 alpha releases ([#57](#57)) ([08b9087](08b9087)) --- Merging this PR will publish a copick-shared-ui alpha prerelease to PyPI. Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
2.0.0-alpha.Nv2.0while leaving stable publication onmainRelease-As: 2.0.0-alpha.1on this PR's release-configuration commit.release-please.manifest.jsonat the last published version (0.7.0) until the release PR updates itmainandv2.0update tracksStack
This is stack layer 4 of 4. It targets
uermel/zarr-v3-p2-validation.If this PR is squash-merged, the resulting commit on
v2.0must retain theRelease-As: 2.0.0-alpha.1footer. Verify that footer before dispatching the release workflow.Documentation is deliberately not part of this alpha-enablement PR. Per the migration rollout, the final README/changelog/claim audit remains a required pass immediately before coordinated stable cutover and does not block ecosystem alpha validation.
Release Please proof
A read-only Release Please dry run against pushed head
2d941cdand the repository's prerelease config produced:This verifies that the footer overrides the normal pre-1.0 calculation and that the first release PR will be
2.0.0-alpha.1; no persistent deprecatedrelease-asconfiguration is needed.Validation
2.0.0-alpha.1action-validatorPart of #52
Part of #53