Skip to content

ci: update VPM repository after successful release - #45

Merged
RamType0 merged 1 commit into
mainfrom
ci/update-vpm-after-release
Nov 4, 2026
Merged

RamType0 merged 1 commit into
mainfrom
ci/update-vpm-after-release

Conversation

@RamType0

@RamType0 RamType0 commented Nov 4, 2026

Copy link
Copy Markdown
Owner

Summary

  • Dispatch RamType0/VpmRepository's build-repository.yml on main after the release build job succeeds.
  • Keep the release job unchanged and give the dispatch job no GITHUB_TOKEN permissions.
  • Use the dedicated VPM_REPOSITORY_TOKEN Actions secret for cross-repository access.

Setup

Before merging, add VPM_REPOSITORY_TOKEN to this repository's Actions secrets: a fine-grained PAT restricted to RamType0/VpmRepository with Actions read/write permission. Secret provisioning is pending and is not included in this PR.

Verification

  • actionlint -shellcheck= .github/workflows/release.yml passed.
  • git diff --check passed.
  • Confirmed the target workflow already supports workflow_dispatch.
  • No release or downstream deployment was triggered during validation. The dispatch requests an update; it does not wait for the downstream run to finish.

@RamType0
RamType0 merged commit c8f4820 into main Nov 4, 2026
12 checks passed
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