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

fix(extension): update tarball filename format #3307

Merged
merged 3 commits into from
Aug 29, 2023

Conversation

smallstepman
Copy link
Contributor

Description

dfinity/dfx-extensions#48 changed how the filename of tarball and the name of the dir directly inside it; they no longer contain the version of the extension (meaning, we're going from {package}-v{version}-{platform}.{ext} to {package}-{platform}.{ext})

Awaits merging of dfinity/dfx-extensions#51 and dfinity/dfx-extensions#50

How Has This Been Tested?

covered by CI

Checklist:

  • The title of this PR complies with Conventional Commits.
  • I have edited the CHANGELOG accordingly.
  • I have made corresponding changes to the documentation.

the tarball no longer contains the version
@smallstepman smallstepman enabled auto-merge (squash) August 28, 2023 16:42
@smallstepman smallstepman force-pushed the mnl/update-extension-tarball-filename branch from 76bd27f to e46e2cc Compare August 29, 2023 13:52
@smallstepman smallstepman merged commit fec1ddc into master Aug 29, 2023
169 checks passed
@smallstepman smallstepman deleted the mnl/update-extension-tarball-filename branch August 29, 2023 14:50
@smallstepman
Copy link
Contributor Author

@ericswanson-dfinity I forgot about auto-merge... do you think this was correct move e46e2cc ? Another option would be to build extensions using older ubuntu (20.04 instead of 22.04)

@ericswanson-dfinity
Copy link
Member

@smallstepman Please change this back to ubuntu 20.04, and build extensions with that too.

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.

2 participants