New FSH Publisher + v1.18.0 #90
Merged
Conversation
This file contains 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
jafeltra
force-pushed
the
new-fsh-publisher
branch
from
1a552d3 to
9a8a801
Compare
cmoesel
previously approved these changes
Sep 18, 2024
cmoesel
approved these changes
Sep 19, 2024
mint-thompson
approved these changes
Sep 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description: This PR adds the new publisher and bumps the version of the extension.
This branch will be merged into
masterand then can be published to the new publisher.Testing Instructions: Make sure I didn't miss an instance of the old publisher.
I believe I can also just publish the extension to the new publisher since that won't affect the old publisher and current extension. If anyone wants to see that as part of testing, let me know.
Related Issue: N/A