[email protected]: Add manifest

[FilipDeVos]

This pull request adds the manifest to install the "mise-en-place" tool from https://github.com/jdx/mise/

Closes #6329

• Use conventional PR title: <manifest-name[@version]|chore>: <general summary of the pull request>
• I have read the Contributing Guide

[FilipDeVos]

/verify

[github-actions]

All changes look good.

Wait for review from human collaborators.

mise

• Description
• License
• Hashes
• Checkver
• Autoupdate
• Autoupdate Hash Extraction

[github-actions]

All changes look good.

Wait for review from human collaborators.

mise

• Description
• License
• Hashes
• Checkver
• Autoupdate
• Autoupdate Hash Extraction

[FilipDeVos]

I am trying to do the right thing with the PR title, but the documentation is contradicting.

• For buckets it says: If it's a new manifest, use : Add version .
• In the PR template it says: use conventional commits.

[o-l-a-v]

If we want mise to be purged if scoop uninstall --purge mise, which I guess we do, then add something like:

{
  "post_uninstall": [
        "if ($purge) {",
        "    $Directories = [string[]](",
        "        ('{0}\\mise' -f $env:LOCALAPPDATA),",
        "        ('{0}\\Temp\\mise' -f $env:LOCALAPPDATA)",
        "    )",
        "    $Directories.ForEach{",
        "        if (Test-Path -Path $_ -PathType 'Container') {",
        "            $null = Remove-Item -Path $_ -Recurse -Force",
        "        }",
        "    }",
        "}"
    ]
}

[nagromc]

I was about to submit a PR; thanks @FilipDeVos!

I suggest two things:

1. Use a more precise description. The About page is pretty good IMO:

   Development environment setup tool

2. Use the full name as the app ID: i.e. mise-en-place.json instead of mise.json

[FilipDeVos]

I noticed that we need to add $env:LOCALAPPDATA\mise\shims to $env:PATH

I'll research a bit what the best way of doing this is.

[o-l-a-v]

Scratch this idea

Maybe "post_install" to add it with PowerShell, and "post_uninstall" to remove it? In user context. Something like this (untested):

[System.Environment]::SetEnvironmentVariable(
   'Path',
   ('{0};{1}\mise\shims' -f [System.Environment]::GetEnvironmentVariable('Path','User'), $env:LOCALAPPDATA),
  'User'
)

---

Edit: Scratch the above, seems Scoop has env_add_path which can be used for this?

• About manifest: https://github.com/ScoopInstaller/Scoop/wiki/App-Manifests
• Examples: https://github.com/search?q=repo%3AScoopInstaller%2FMain%20env_add_path&type=code

[FilipDeVos]

env_add_path only supports folders under the installation folder I think.

[FilipDeVos]

I think this commit does the trick.

[FilipDeVos]

/verify

[github-actions]

Your changes do not pass checks.

mise-en-place

• Description
• License
• Hashes
• Checkver
• Autoupdate
• Autoupdate Hash Extraction

[FilipDeVos]

/verify

[github-actions]

All changes look good.

Wait for review from human collaborators.

mise-en-place

• Description
• License
• Hashes
• Checkver
• Autoupdate
• Autoupdate Hash Extraction

[jdx]

@FilipDeVos thank you so much for doing this, I was literally starting to do it myself when I thought to check if maybe someone made a PR already.

It's great you added the shims, though in the future if we get powershell support for mise activate we'll need to probably rethink that. I still think it's good to auto-add shims now though.

I am also working on winget (though it's failing and idk why) and have created a github action to automatically bump it on releases. Do you think something similar for scoop would be good?

I know these are unrelated to scoop but we also have chocolatey which is community maintained, but I have noticed it has been quite out of date. I think if you or I did some of the legwork on automatically bumping in gha it would probably be good to try to knock out all 3.

[FilipDeVos]

@jdx scoop auto-updates the version, that is what the checkver logic is for. So there is no need to make pipelines.

Once the PR is merged in main it will start bumping the version automatically.

I can take a look at the winget/chocolatey Manifests if you have a branch somewhere, but I'm not interested in being maintainer of that stuff.

[jdx]

totally understand, if you wouldn't mind having a look at my winget PR to see if there is anything obviously wrong I would definitely appreciate it!

[chawyehsu]

The name mise is available to occupied, it should be used as the manifest name to provide a max consistency if it's used on other pms.

[chawyehsu]

I am trying to do the right thing with the PR title, but the documentation is contradicting.

• For buckets it says: If it's a new manifest, use : Add version .
• In the PR template it says: use conventional commits.

There's no contradicting, Add version could be the PR summary <general summary of the pull request>, [@version] is optional.

• [email protected]: Add manifest good
• mise: Add version 2024.12.3 also good
• Add mise version 2024.12.3 bad
• Add mise manifest worst

[gatspy]

No matches found.
scoop search mise # WARN No matches found.

[nagromc]

No matches found. scoop search mise # WARN No matches found.

It has not been merged yet.