Skip to content

feat(release): rename future assets to jevwise - #74

Merged
benbenbang merged 1 commit into
mainfrom
feature/26-release-rename
Oct 9, 2026
Merged

benbenbang merged 1 commit into
mainfrom
feature/26-release-rename

Conversation

@benbenbang

Copy link
Copy Markdown
Member

Use jevwise_ for future releases while preserving published v1.0.0, v1.1.0 and v1.2.0 assets without overwriting them. Prefer the exact primary updater asset and use jev_ only when it is absent, preserving validation, atomic replacement, the installed basename, and no alias or deletion. Document manual migration for old clients and cover publisher and downloader compatibility paths.

Use `jevwise_` for future releases while preserving published v1.0.0, v1.1.0 and v1.2.0 assets without overwriting them. Prefer the exact primary updater asset and use `jev_` only when it is absent, preserving validation, atomic replacement, the installed basename, and no alias or deletion. Document manual migration for old clients and cover publisher and downloader compatibility paths.
@benbenbang
benbenbang enabled auto-merge (rebase) October 9, 2026 04:38
@github-actions github-actions Bot added documentation Improvements or additions to documentation triage labels Oct 9, 2026
@benbenbang
benbenbang merged commit 0ce9177 into main Oct 9, 2026
5 checks passed
@benbenbang
benbenbang deleted the feature/26-release-rename branch October 9, 2026 04:39
@ptah-bw-technical-app

Copy link
Copy Markdown

🎉 This PR is included in version 1.3.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation released triage

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant