Skip to content

ci: auto-publish on v4 merge#111

Merged
steveworley merged 1 commit intov4from
ci/auto-publish-on-merge
Mar 3, 2026
Merged

ci: auto-publish on v4 merge#111
steveworley merged 1 commit intov4from
ci/auto-publish-on-merge

Conversation

@steveworley
Copy link
Contributor

Summary

  • Publish workflow now triggers automatically on push to v4 (instead of manual dispatch only)
  • Detects dependabot merges via commit message and auto-bumps the patch version (e.g. 4.11.0 → 4.11.1)
  • Portal/SDK PRs publish as-is since the version is already set by the generation pipeline
  • workflow_dispatch retained as a manual fallback
  • paths-ignore prevents publishing on workflow, docs, or metadata-only changes

Notes

  • First merge: This PR only changes .github/**, which is in paths-ignore, so merging it will NOT trigger a publish run. This is expected.
  • GITHUB_TOKEN re-trigger safety: The dependabot version bump commit uses GITHUB_TOKEN, which does not re-trigger workflows. The duplicate-version check provides an additional safety net.
  • npm auth: Uses OIDC (no secrets/tokens), matching the existing approach.

Test plan

  • Verify test workflow passes on this PR
  • After merge, use workflow_dispatch to confirm the workflow runs correctly
  • On next dependabot PR merge, verify patch bump + auto-publish works
  • On next SDK PR merge, verify direct publish works

- Trigger on push to v4 (with paths-ignore for workflow/docs changes)
- Detect dependabot merges and auto-bump patch version
- Retain workflow_dispatch as manual fallback
@steveworley steveworley requested a review from stooit March 1, 2026 05:19
@steveworley steveworley merged commit 8f31738 into v4 Mar 3, 2026
3 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.

2 participants