Add versionPrefix to vip-block-data-api configuration - #97
Merged
Merged
Conversation
Contributor
Author
|
@ingeniumed Something to watch out for in Automattic/vip-governance-plugin#122! We can either change the configuration to drop the |
maxschmeling
approved these changes
Jan 7, 2026
This was referenced Jan 7, 2026
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
2 participants
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.
We recently added release automation to the VIP Block Data API. The new release uses a
vprefix, e.g.v1.4.6for tags, but prior releases only used the bare version number as a tag (1.4.5).Due to the change, this has resulted in the Block Data API failing to upgrade in the integration center. I'm opting to keep the
vprefix and update our configuration here.