feat: un-gate fishing-activity-gfw plugin (keys wired, needsKey false, 1.1.0) - #70
Open
silvertakana wants to merge 1 commit into
Open
silvertakana wants to merge 1 commit into
silvertakana wants to merge 1 commit into
Conversation
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.
Un-gates the Fishing Activity (GFW) plugin so the CI publish workflow can release it to npm.
Background: the plugin shipped on main at v1.0.0 with needsKey set to true in package.json, a publish-guard mechanic that kept the publish workflow from publishing it. The required third-party API key has now been obtained and verified, so this branch:
No runtime behavior changes; the plugin frontend code is unchanged.