chore: Release 1.5.0 #268
Merged
chore: Release 1.5.0 #268
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
This previously focused exclusively on shell hooks and used them to run a service. This now shows a user how to leverage the hook, profile, and vars sections to customize their shell environment in an activated environment. There is now a `lint` alias in the environment to make it easier to remember the linter command.
This PR was automatically created by [Update workflow](https://github.com/flox/floxdocs/actions/workflows/update.yml). Co-authored-by: FloxBot <[email protected]>
There has been some confusion over Flox not being able to run as non-root in containers, see flox/flox#1188
Document container installs are root only
…in the all group (#254) Bumps the all group with 1 update: [mkdocs-include-markdown-plugin](https://github.com/mondeja/mkdocs-include-markdown-plugin). Updates `mkdocs-include-markdown-plugin` from 7.1.5 to 7.1.6 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/mondeja/mkdocs-include-markdown-plugin/releases">mkdocs-include-markdown-plugin's releases</a>.</em></p> <blockquote> <h2>v7.1.6</h2> <h3>Bug fixes</h3> <ul> <li>Fix internal anchor in included file incorrectly rewritten.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/mondeja/mkdocs-include-markdown-plugin/commit/1062404c833381c0c33588c8ee606ce6c9a2ed8e"><code>1062404</code></a> Fix internal anchor in included file incorrectly rewritten (<a href="https://redirect.github.com/mondeja/mkdocs-include-markdown-plugin/issues/267">#267</a>)</li> <li>See full diff in <a href="https://github.com/mondeja/mkdocs-include-markdown-plugin/compare/v7.1.5...v7.1.6">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>
…roup (#263) Bumps the all group with 1 update: [pymdown-extensions](https://github.com/facelessuser/pymdown-extensions). Updates `pymdown-extensions` from 10.15 to 10.16 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/facelessuser/pymdown-extensions/releases">pymdown-extensions's releases</a>.</em></p> <blockquote> <h2>10.16</h2> <ul> <li><strong>NEW</strong>: Add early support for Python 3.14.</li> <li><strong>NEW</strong>: Drop support for Python 3.8.</li> <li><strong>NEW</strong>: Snippets: Added <code>max_retries</code> and <code>backoff_retries</code> options to configure new retry logic for HTTP 429 errors (Too Many Requests client error).</li> <li><strong>NEW</strong>: Caption: Prefix templates are now preserved exactly as specified allowing the insertion of HTML tags if desired.</li> <li><strong>FIX</strong>: Caption: Fix issue where manual numbers in auto were not respected appropriately.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/facelessuser/pymdown-extensions/commit/7d3d4f990463e50b1ba1e20830832285d92990c7"><code>7d3d4f9</code></a> Add early support for Python 3.14 (<a href="https://redirect.github.com/facelessuser/pymdown-extensions/issues/2697">#2697</a>)</li> <li><a href="https://github.com/facelessuser/pymdown-extensions/commit/beb841e6f968b81403166d685b083fe2bde84bbc"><code>beb841e</code></a> Docs: Update JS deps</li> <li><a href="https://github.com/facelessuser/pymdown-extensions/commit/620d7fded457a0b5317019fa461a27f484a0d3d4"><code>620d7fd</code></a> Docs: update JS deps</li> <li><a href="https://github.com/facelessuser/pymdown-extensions/commit/a49f32aa4ac91d97c7c10c9abe7f654b5ec802e5"><code>a49f32a</code></a> Refactor for mypy issue</li> <li><a href="https://github.com/facelessuser/pymdown-extensions/commit/52a481b5591879f49baffecf4275f351d27a3759"><code>52a481b</code></a> Docs: update JS dependencies</li> <li><a href="https://github.com/facelessuser/pymdown-extensions/commit/2a1828accdc2371d97610fbbb574dd878e090b54"><code>2a1828a</code></a> Allow raw HTML in caption prefix (<a href="https://redirect.github.com/facelessuser/pymdown-extensions/issues/2679">#2679</a>)</li> <li><a href="https://github.com/facelessuser/pymdown-extensions/commit/fbf4bf22da3bc864f24b4ee6a2c05b145fb6c304"><code>fbf4bf2</code></a> Fix issue where manual captions in auto were not respected properly (<a href="https://redirect.github.com/facelessuser/pymdown-extensions/issues/2678">#2678</a>)</li> <li><a href="https://github.com/facelessuser/pymdown-extensions/commit/70cf820aae36d57cf493ca9c8c2e24ab11c6c445"><code>70cf820</code></a> Fix spelling of marketplace for GitHub (<a href="https://redirect.github.com/facelessuser/pymdown-extensions/issues/2674">#2674</a>)</li> <li><a href="https://github.com/facelessuser/pymdown-extensions/commit/553251d5a68999a95b71bd155fa83b3f9a4f7997"><code>553251d</code></a> Add retry logic for rate limited HTTP errors (429) (<a href="https://redirect.github.com/facelessuser/pymdown-extensions/issues/2669">#2669</a>)</li> <li><a href="https://github.com/facelessuser/pymdown-extensions/commit/bd2f267557e27d1482db5ad7c0a9db4c619a6004"><code>bd2f267</code></a> Drop Python 3.8 (<a href="https://redirect.github.com/facelessuser/pymdown-extensions/issues/2654">#2654</a>)</li> <li>Additional commits viewable in <a href="https://github.com/facelessuser/pymdown-extensions/compare/10.15...10.16">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>
ℹ️ This merges into `build-preview` which will be published at https://build-preview--floxdocs.netlify.app/ Add a sub-section about the other `sandbox=pure` mode that we currently support, including the caveat that networking access is only sandboxed on Linux. I've created a couple of new bugs/ehancements in the process: - flox/flox#2461 - flox/flox#2462 Plus a few typos and tweaks that are in separate commits.
I got confused and used the attr_path in `runtime-packages` at first. Thought it would be good to make this explicit and update the example to reflect the difference. I question using the `hello-go` package, but wanted a different install-id from the pkg-path.
This change reworks the existing build concept page and adds a publishing concept page. In the future there will be links to other pages that are currently in progress.
feat: add JVM build example
This is tautological --------- Signed-off-by: barstoolbluz <[email protected]> Co-authored-by: barstoolbluz <[email protected]> Co-authored-by: Thomas Bereknyei <[email protected]> Co-authored-by: Zach Mitchell <[email protected]>
After adding a new trusted key you need to restart the Nix daemon, and this was not previously mentioned in the docs.
This moves the existing "publishing" cookbook pages and creates a new "known issues" page to a new "customer" section. This section isn't linked in the sidebar, but can still be linked to if the URL is known. Note that the pages in this section are still world-readable if you know the URL.
Describe why you would choose one over the other and what the trade-offs are.
chore: add customer section
Wordsmithed with Yannik.
chore: artifact -> package
This was fixed in flox/flox#3132 Removing this required restructing the paragraphs.
feat: update build concept page
feat: describe Rust build complications
This explains the RBAC model for orgs, and replaces the bits about contacting us to make changes with an explanation of how to manage the org in FloxHub.
feat: add build and publish docs
Our verison constraint on the `python` package was holding everything back. Instead of using a version constraint to install Python 3.11.* I instead install the `python311` package. This is the result of the upgrade (copied from the dry run): ``` Dry run: Upgrades available for 9 package(s) in 'floxdocs': - coreutils: 9.5 -> 9.7 - d2: 0.6.5 -> 0.7.0 - findutils: 4.9.0 -> 4.10.0 - gnused: 4.9 - gnutar: 1.35 - pandoc: 3.1.11.1 -> 3.6 - pngquant: 3.0.3 - poetry: 1.8.3 -> 2.1.3 - python: python3-3.11.9 -> python3-3.11.12 To apply these changes, run upgrade without the '--dry-run' flag. ```
This brings the activation hooks in line with those generated by flox#3174.
chore: fix package upgrades
This adds instructions for pure builds in various languages since it may not be obvious how to accomplish the vendoring step or do a multi-stage build.
stahnma
approved these changes
Jun 25, 2025
stahnma
approved these changes
Jun 25, 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.