chore: sync plugin.json version to v1.2.0#17
Merged
Conversation
Manual sync (the sync-plugin-version.yml workflow did not fire on v1.2.0 tag push despite matching the same trigger as v1.1.0 — GitHub Actions glitch). Same outcome as the auto-sync workflow would produce. Follow-up issue to be filed to investigate why the workflow didn't trigger on this tag push. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Manual sync — workflow-plugin-aws v1.2.0 tag push did not trigger sync-plugin-version.yml (GitHub Actions glitch; same workflow fired correctly on v1.1.0 from yesterday). One-line plugin.json version bump. Same outcome as auto-sync.
Releases asset state verified clean post-tag-push:
Follow-up issue to be filed to investigate the workflow non-trigger.