Skip to content

chore: sync plugin.json version to v1.0.4#19

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
chore/sync-plugin-version-v1.0.4
Closed

chore: sync plugin.json version to v1.0.4#19
github-actions[bot] wants to merge 1 commit into
mainfrom
chore/sync-plugin-version-v1.0.4

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

Triggered by release v1.0.4. Auto-sync to prevent drift. Closes workflow-registry#37.

@intel352
Copy link
Copy Markdown
Contributor

Closing as superseded. These auto-sync PRs would DOWNGRADE plugin.json from v1.1.1 to v1.0.x (v1.0.2/v1.0.3/v1.0.4 ranges below the prior v1.1.1 tag).

Background: v1.1.0 + v1.1.1 git tags exist but their GoReleaser runs FAILED (npm 401 + cp cwd + dirty-state bugs — all fixed by PRs #14 + #16 + #18). My recent sweep accidentally cut v1.0.1 → v1.0.2 → v1.0.3 → v1.0.4 (the semver line BELOW the prior failed tags), creating a versioning mess.

Recovery: cutting v1.1.2 now (above prior v1.1.1) via the now-fixed release workflow. The next auto-sync PR will bump plugin.json from 1.1.1 → 1.1.2 (semver forward, no downgrade).

Apologies for the confusion.

@intel352 intel352 closed this May 16, 2026
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