Skip to content

chore: install Tinty from GitHub releases - #45

Open
Elliot-32 wants to merge 4 commits into
masterfrom
chore/tinty-github-backend
Open

Elliot-32 wants to merge 4 commits into
masterfrom
chore/tinty-github-backend

Conversation

@Elliot-32

Copy link
Copy Markdown
Owner

Summary

  • install Tinty 0.34.1 from its official GitHub release binaries instead of the Cargo backend
  • update Omarchy disable_tools to use the new backend key
  • regenerate mise.lock with the official release assets and checksums

RustScan stays on cargo:rustscan: upstream currently documents Cargo as its only officially supported installation method, while Tinty publishes platform-specific release binaries suitable for mise's GitHub backend.

Lockfile

The lockfile was regenerated from the existing clean lock state. The net lock diff is limited to removing the old 5-line cargo:tinty entry and adding the 50-line github:tinted-theming/tinty platform metadata; no unrelated Aqua/Cosign metadata churn is included.

Copy link
Copy Markdown
Owner Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Breezy!

Reviewed commit: 8cd9e1e29c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

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.

1 participant