Conversation
In order to fix jdx#36
| autoload-env: | ||
| description: "Automatically load mise env vars into GITHUB_ENV" | ||
| required: false | ||
| default: "false" |
There was a problem hiding this comment.
I would default to true and we can do a semver major bump
| required: false | ||
| default: "true" | ||
| description: If true (default), fetch the mise binary from GitHub. If false and using the latest version, fetch from mise.jdx.dev instead. | ||
| autoload-env: |
|
needs tests |
|
@jdx not sure how to add test to those, care to help me/show me where and how it can be done? |
|
@jdx I tried to edit this locally to run |
|
my guess is your node version is out of date. You can find existing tests in github actions. |
|
@jdx okay I have added a test |
|
It seems working, just added a test env |
|
I'm not sure if It might collide with the Line 71 in e7e4845 |
|
@risu729 not sure about what you're saying? would you mind updating the PR for this? shouldn't any path extension be already added to the .env when using |
|
Sorry, I was wrong. It seems |
that would probably be quite hard to support, we should document this as a gap though |
--- ## [3.0.0](https://github.com/jdx/mise-action/compare/v2.4.4..v3.0.0) - 2025-08-18 ### 🚀 Features - **breaking** export env vars from mise.toml (#241) by [@maelp](https://github.com/maelp) in [#241](#241) ### New Contributors * @maelp made their first contribution in [#241](#241) <!-- generated by git-cliff --> Co-authored-by: mise-en-dev <[email protected]>
Solve #36
BREAKING CHANGE: we're defaulting this behavior to
true