-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
engineering#245 - change push conditions to require a tag AND master branch #168
base: master
Are you sure you want to change the base?
Conversation
@Samkeer1 not sure what you mean by a PR. This is the only repo, it's published via |
@texastoast I'm suggesting that we make a suggestion to change the copy that hex provides, because it could be more descriptive. |
@Samkeer1 makes sense to me, I'd say call your shot and if you think it needs to be more descriptive, make a PR. |
@@ -3,7 +3,6 @@ name: Publish | |||
on: | |||
push: | |||
tags: [ 'v*.*.*' ] | |||
branches: master |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change is in master now as of #171
@@ -14,6 +13,7 @@ jobs: | |||
uses: ./.github/workflows/test.yml | |||
publish: | |||
needs: test | |||
if: ${{ github.ref_name == 'master' }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this is necessary. In fact, we could decide to maintain multiple branches, for example if we went 3.0 on master
but still wanted to allow bugfixes to be released to 2.X.
@Samkeer1 do you mind if I close this branch? |
Response to failed publish:
https://github.com/revelrylabs/ecto_soft_delete/actions/runs/8571557508/job/23492117202
The error indicates we're trying to re-publish an existing version after the hour window of published version update availability. Perhaps we can open a https://github.com/hexpm/hexpm PR that checks to see if attempts to publish packages are from over x amount of time after a publish, and if so, displays separate or even additional error copy (e.g "further updates to this package will require a package version update")