Skip to content
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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Samkeer1
Copy link
Contributor

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")

@Samkeer1 Samkeer1 changed the title change push conditions to require a tag AND master branch engineering#245 - change push conditions to require a tag AND master branch Apr 19, 2024
@Samkeer1 Samkeer1 requested a review from texastoast April 22, 2024 14:11
@texastoast
Copy link

@Samkeer1 not sure what you mean by a PR. This is the only repo, it's published via mix hex.publish. See https://hex.pm/docs/publish

@Samkeer1
Copy link
Contributor Author

@texastoast I'm suggesting that we make a suggestion to change the copy that hex provides, because it could be more descriptive.

@texastoast
Copy link

@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
Copy link
Contributor

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' }}
Copy link
Contributor

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.

@stuartjohnpage
Copy link
Contributor

@Samkeer1 do you mind if I close this branch?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants