Add PGXN Meta.json and release workflow #54
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
|
Since this project doesn't have a |
olirice
approved these changes
Apr 12, 2024
|
fantastic, thank you we'll make sure this pushes to pgxn with the next release |
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.
Add a PGXN Meta spec file and a workflow to release the on PGXN for tags that look like a semantic version. Before you tag a release to deploy to pgxn, request an account. I will approve ASAP. Then set your password and add the
PGXN_USERNAMEandPGXN_PASSWORDworkflow secrets to this repository (or your or settings to apply to all your extensions that use a workflow like this).