Skip to content

ci(release): reference the shared release workflows through v1 - #25

Merged
Upd4ting merged 1 commit into
mainfrom
ci/release-workflow-v1
Sep 23, 2026
Merged

Upd4ting merged 1 commit into
mainfrom
ci/release-workflow-v1

Conversation

@Upd4ting

Copy link
Copy Markdown
Member

Summary

Reference the organization reusable release workflow (AntelopeJS/.github/.github/workflows/release-npm-public.yml) through the moving major tag @v1 instead of a pinned commit SHA. The organization maintains v1 as a tag re-pointed to the latest backward-compatible version of the reusable workflows (see "Release channels" in the organization CONTRIBUTING.md), so this repository picks up compatible fixes such as release: v${version} commits on the next channel and optional service containers without further pin bumps.

No other change: release-it config, dependencies and changelog are untouched.

Related issue

N/A — organization-wide alignment on the v1 release channel of the shared workflows.

Verification

  • grep -rn 'AntelopeJS/.github/.github/workflows' .github/workflows shows only the @v1 reference.
  • actionlint .github/workflows/release.yml reports no issues.
  • YAML parses successfully.

Checklist

  • The pull request title follows Conventional Commits.
  • I added or updated tests when behavior changed. (N/A: workflow reference only)
  • I updated documentation when users or contributors are affected. (N/A)
  • I documented breaking changes and migration steps. (N/A: no breaking change)
  • I did not include credentials or unrelated changes.

@Upd4ting
Upd4ting merged commit 5e06f7a into main Sep 23, 2026
2 checks passed
@Upd4ting
Upd4ting deleted the ci/release-workflow-v1 branch September 23, 2026 17:50
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