Skip to content

Tighten dependencies to latest/greatest and pin fez version#185

Open
lizmat wants to merge 1 commit intoskaji:mainfrom
lizmat:tighten-dependencies
Open

Tighten dependencies to latest/greatest and pin fez version#185
lizmat wants to merge 1 commit intoskaji:mainfrom
lizmat:tighten-dependencies

Conversation

@lizmat
Copy link
Contributor

@lizmat lizmat commented Aug 5, 2025

The latest version of fez has a slightly different API which may cause issues with App::Mi6. It therefore felt safer to pin it to the last version prior to version 100 until it has been determined that there are no issues with the latest fez version.

Tightened up other dependencies, because that's a good thing to do in a world where accountability is becoming more important.

Also updated copyright year and added tags

The latest version of fez has a slightly different API which *may*
cause issues with App::Mi6.  It therefore felt safer to pin it to
the last version prior to version 100 until it has been determined
that there are no issues with the latest fez version.

Tightened up other dependencies, because that's a good thing to do
in a world where accountability is becoming more important.

Also update copyright year and add tags
@skaji
Copy link
Owner

skaji commented Aug 5, 2025

Thanks for the PR. I gave it a try and was able to perform a release successfully using mi6 together with fez v100. Based on that, it seems there’s no need to pin the version.

One thing to note: after upgrading fez to v100, it seems necessary to run fez login manually once before running mi6 release.

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