Skip to content

Unify release options across extension, style and language-pack scripts - #42

Merged
bonelifer merged 1 commit into
mainfrom
unify-release-options
Oct 28, 2026
Merged

bonelifer merged 1 commit into
mainfrom
unify-release-options

Conversation

@bonelifer

Copy link
Copy Markdown
Contributor

All three package scripts now use local HEAD by default, with --remote to package GitHub's pinned default-branch commit. Each supports --create, --release, --dry-run, --force, --repo, and --output; existing --gh-release and --output-dir aliases remain supported. The separate git-release-api.sh entry point is retired.

Explicit --force permits replacing an existing tag and release ZIP while preserving stable/prerelease classification and unrelated assets. Rolling development releases retain their existing behavior, and GitHub-enforced protections remain effective. Package layouts and language-pack validation are preserved. README, help, CI inputs, and regression coverage are updated; matching Wiki documentation will follow the merged commands.

Codex ran ShellCheck and the local packaging/argument regressions successfully. Expanded offline tests cover remote sources, forced replacement, failure recovery, and the language-pack validation gate.


Investigated and written by Codex on behalf of William Jacoby (bonelifer).

@bonelifer
bonelifer merged commit 779c648 into main Oct 28, 2026
1 check passed
@bonelifer
bonelifer deleted the unify-release-options branch October 28, 2026 16:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant