Skip to content

Meta: Improve release workflow#6145

Merged
fregante merged 10 commits into
mainfrom
new-release
Feb 20, 2023
Merged

Meta: Improve release workflow#6145
fregante merged 10 commits into
mainfrom
new-release

Conversation

@fregante
Copy link
Copy Markdown
Member

@fregante fregante commented Nov 6, 2022

Reopening of #6114

This workflow doesn't work and needs fixing.

Copy link
Copy Markdown
Member Author

@fregante fregante left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See the last run for details: https://github.com/refined-github/refined-github/actions/runs/3403316739/jobs/5659762409

I had to stop it once it got to the submit job.

I think the main issue is my misunderstanding of how core.exportVariable works in https://github.com/fregante/daily-version-action. Somehow the exported ENV isn't actually available outside the action

Comment thread .github/workflows/release.yml Outdated
with:
name: built
path: ${{ env.DIRECTORY }}
- if: env.DAILY_VERSION_CREATED
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't exist so the tag is created by fregante/daily-version-action but the release isn't

See:

Comment thread .github/workflows/release.yml Outdated
- uses: actions/download-artifact@v3
- name: Submit to Mozilla
if: matrix.command == 'firefox'
run: cd artifacts/built && npx web-ext-submit@7
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The built artifact is created correctly in the previous job, but artifacts/built doesn't exist. I assume that's how a parameter-less actions/download-artifact would work.

Comment thread .github/workflows/release.yml
gh release create "$DAILY_VERSION" --generate-notes refined-github-local-install.zip

Submit:
needs: Version
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The condition below is fired even if needs.Version.outputs.created isn't set. The intention was to always attempt to submit to the stores even on re-runs, but I don’t think this ever worked correctly and should be dropped for now.

@fregante fregante closed this Dec 29, 2022
@FloEdelmann FloEdelmann deleted the new-release branch December 29, 2022 21:47
@fregante fregante restored the new-release branch February 12, 2023 12:32
@fregante fregante reopened this Feb 12, 2023
@fregante fregante added meta Related to Refined GitHub itself and removed help wanted labels Feb 12, 2023
@fregante fregante marked this pull request as ready for review February 12, 2023 13:00
Copy link
Copy Markdown
Member Author

@fregante fregante left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should now be ready for merge. I'll keep it here until the next release.

After that, the next step would be fregante/browser-extension-template#49 (comment)

steps:
- uses: actions/checkout@v3
with:
fetch-depth: 20
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only needed by the previous releaser https://github.com/fregante/release-with-changelog

run: npm test
- name: Create tag if necessary
uses: fregante/daily-version-action@v2
- name: Update manifest.json with version ${{ env.DAILY_VERSION}}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nitpic:

Suggested change
- name: Update manifest.json with version ${{ env.DAILY_VERSION}}
- name: Update manifest.json with version ${{ env.DAILY_VERSION }}

@fregante fregante merged commit 60ac04e into main Feb 20, 2023
@fregante fregante deleted the new-release branch February 20, 2023 07:16
@fregante
Copy link
Copy Markdown
Member Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

meta Related to Refined GitHub itself

Development

Successfully merging this pull request may close these issues.

2 participants