chore: release 1.4.4 #245
Merged
chore: release 1.4.4 #245
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…12 in the all group (#224) Bumps the all group with 1 update: [trove-classifiers](https://github.com/pypa/trove-classifiers). Updates `trove-classifiers` from 2025.5.1.12 to 2025.5.9.12 <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pypa/trove-classifiers/commit/b67299df973749f590c41d02329ccb9ca6af5054"><code>b67299d</code></a> Add trove classifier for GraalPython (<a href="https://redirect.github.com/pypa/trove-classifiers/issues/188">#188</a>)</li> <li><a href="https://github.com/pypa/trove-classifiers/commit/331838aaea0eea6374e4e51e8fe05e13bf7e4957"><code>331838a</code></a> feat: add free-threading classifiers (<a href="https://redirect.github.com/pypa/trove-classifiers/issues/195">#195</a>)</li> <li><a href="https://github.com/pypa/trove-classifiers/commit/00f84964bf172aa9274343291073136a1256abab"><code>00f8496</code></a> Fix python usage in makefile (<a href="https://redirect.github.com/pypa/trove-classifiers/issues/217">#217</a>)</li> <li><a href="https://github.com/pypa/trove-classifiers/commit/fca1f10d735d84c3cdb5dfc409959d3cb8ed2e1c"><code>fca1f10</code></a> Add several missing languages (<a href="https://redirect.github.com/pypa/trove-classifiers/issues/215">#215</a>)</li> <li><a href="https://github.com/pypa/trove-classifiers/commit/38454c06aca1acfc3acfcf9eb63c12f2979c4fc3"><code>38454c0</code></a> Add Trove classifier for Python 3.15 (<a href="https://redirect.github.com/pypa/trove-classifiers/issues/213">#213</a>)</li> <li>See full diff in <a href="https://github.com/pypa/trove-classifiers/compare/2025.5.1.12...2025.5.9.12">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
chore: Update Flox environment
Bumps the all group with 1 update: [cairosvg](https://github.com/Kozea/CairoSVG). Updates `cairosvg` from 2.7.1 to 2.8.2 - [Release notes](https://github.com/Kozea/CairoSVG/releases) - [Changelog](https://github.com/Kozea/CairoSVG/blob/main/NEWS.rst) - [Commits](Kozea/CairoSVG@2.7.1...2.8.2) --- updated-dependencies: - dependency-name: cairosvg dependency-version: 2.8.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: all ... Signed-off-by: dependabot[bot] <[email protected]> Signed-off-by: Tom Bereknyei <[email protected]>
chore(deps): bump cairosvg from 2.7.1 to 2.8.2 in the all group
Signed-off: Tom Bereknyei <[email protected]>
chore: Update Flox environment
The previous contents were a v0 pkgdb lock which is no longer in use or supported. I've extracted a small subset of relevant fields from a current lockfile that installs NodeJS.
Instead of the duplicate and potentially out-of-date content in the manfiest concepts which will be removed in a subsequent commit.
In preperation for linking and redirect to them. The previous versions were quite wordy when rendered above the sections, in the side navbar, and as anchors like `#environment-manifest-floxenvmanifesttoml`. Technically this will break existing links in the wild but I can't see anywhere that we currently reference the anchors ourselves.
The `/concepts/manifest` page had content that overlapped with both: - `manifest.toml` which contains a more complete listing of all the currently supported sections. - `environments` which describes the files stored in `.flox/env/` So merge it with environments, introduce the basic format and how to edit, then link out to `manifest.toml` for more details. The old URL will be redirected using the functionality that was added in 91141a7. It's worth noting that this doesn't return a 301 response because the redirect is performed client-side from static content: % http :8000/docs/concepts/manifest/ HTTP/1.0 200 OK Content-Length: 1280 Content-Type: text/html Date: Thu, 15 May 2025 09:35:46 GMT Server: WSGIServer/0.2 CPython/3.11.9 <!doctype html> <html lang="en"> <head> <meta charset="utf-8"> <title>Redirecting...</title> <link rel="canonical" href="../environments/#files-manifest-toml"> <script>var anchor=window.location.hash.substr(1);location.href="../environments/#files-manifest-toml"+(anchor?"#"+anchor:"")</script> <meta http-equiv="refresh" content="0; url=../environments/#files-manifest-toml"> </head> <body> You're being redirected to a <a href="../environments/#files-manifest-toml">new destination</a>. <script> … However it appears that search engines do treat this is a permanent redirect (https://stackoverflow.com/a/19717455) and we can't redirect to a new anchor using Netlify server-side redirects because they are a client-side only concept (not sent as part of the request). I don't think that we necessarily need to change the link from the `flox init` templated manifest because the original URL is more concise, even if it doesn't fit within the structure of the docs.
concepts: Merge manifest concept into environments
rossturk
approved these changes
Jun 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.