chore: Release 1.3.12 #132
Merged
Conversation
This file contains 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
Bumps the all group with 2 updates in the / directory: [pymdown-extensions](https://github.com/facelessuser/pymdown-extensions) and [trove-classifiers](https://github.com/pypa/trove-classifiers). Updates `pymdown-extensions` from 10.13 to 10.14 <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.14</h2> <ul> <li><strong>NEW</strong>: Blocks.HTML: Add new <code>custom</code> option to specify tags and the assumed handling for them when automatic mode is assumed. This can also be used to override the handling for recognized tags with automatic handling.</li> <li><strong>FIX</strong>: Fix tests to pass with Pygments 2.19+.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/facelessuser/pymdown-extensions/commit/5e9c79bc14b2db147803f4f0e5e2bf71fbf0c7cb"><code>5e9c79b</code></a> Docs: Update rollup</li> <li><a href="https://github.com/facelessuser/pymdown-extensions/commit/5f05bc90e85a1b85c042a933e14d59b7fa861bf5"><code>5f05bc9</code></a> Remove unnecessary include</li> <li><a href="https://github.com/facelessuser/pymdown-extensions/commit/e823ada7a5be4d198326d60497a29c72322741e0"><code>e823ada</code></a> Add "steps" list CSS</li> <li><a href="https://github.com/facelessuser/pymdown-extensions/commit/5c38bfc0fbaf737e904d4a317c141fbcbd4f5dc3"><code>5c38bfc</code></a> Add support to handle custom HTML tags (<a href="https://redirect.github.com/facelessuser/pymdown-extensions/issues/2559">#2559</a>)</li> <li><a href="https://github.com/facelessuser/pymdown-extensions/commit/dc2cda923ebcd83564c186c11180e35021beb022"><code>dc2cda9</code></a> Bump sass from 1.83.0 to 1.83.1 (<a href="https://redirect.github.com/facelessuser/pymdown-extensions/issues/2556">#2556</a>)</li> <li><a href="https://github.com/facelessuser/pymdown-extensions/commit/4745949c8c46fab76ce188562b7b05f42a0b8ac0"><code>4745949</code></a> Test with latest Pygments and fix related issues (<a href="https://redirect.github.com/facelessuser/pymdown-extensions/issues/2558">#2558</a>)</li> <li>See full diff in <a href="https://github.com/facelessuser/pymdown-extensions/compare/10.13...10.14">compare view</a></li> </ul> </details> <br /> Updates `trove-classifiers` from 2024.10.21.16 to 2025.1.15.22 <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pypa/trove-classifiers/commit/5e6ed293a095c9a335198907911028108b38a747"><code>5e6ed29</code></a> Add CUDA 12.6 classifier (<a href="https://redirect.github.com/pypa/trove-classifiers/issues/203">#203</a>)</li> <li><a href="https://github.com/pypa/trove-classifiers/commit/28d3e615a2b449f2fc0eabcf4d4578db7dbe0dc8"><code>28d3e61</code></a> Remove unused and "Voluntarily retired" licenses (<a href="https://redirect.github.com/pypa/trove-classifiers/issues/202">#202</a>)</li> <li><a href="https://github.com/pypa/trove-classifiers/commit/c79c976dd1f3ca8cbd1f462d59823df61db7e259"><code>c79c976</code></a> Add upcoming django CMS version (<a href="https://redirect.github.com/pypa/trove-classifiers/issues/198">#198</a>)</li> <li><a href="https://github.com/pypa/trove-classifiers/commit/82307b3772085ca434c4e5cf13192ea6aaac21b5"><code>82307b3</code></a> Add term for quantum computing (<a href="https://redirect.github.com/pypa/trove-classifiers/issues/201">#201</a>)</li> <li>See full diff in <a href="https://github.com/pypa/trove-classifiers/compare/2024.10.21.16...2025.1.15.22">compare view</a></li> </ul> </details> <br /> 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>
I want `gitignore` support from `markdownlint-cli2` but it wasn't available in the version that was pinned by `python.version` in the `toplevel` package group. I've moved `lychee` to a new group at the same time because it felt weird having a group for a single package and I can safely verify that these don't introduce any breaking changes.
This fixes a bug whereby the globs were being incorrectly expanded by the shell before being passed to `markdownlint-cli2` because they weren't quoted as the docs suggest. Depending on the shell in use this could cause it to: - incorrectly miss nested directories like `docs/tutorials/migrations` - semi-correctly miss `docs/reference/command-reference` if the glob was expanded before `flox activate` copies the dir from `flox/flox`
We don't want to lint `docs/reference/command-reference` because the files are already committed and copied from `flox/flox`. We may choose to apply linting there separately. We could use `!docs/reference/command-reference` in the glob patterns but it feels more reliable to depend on the gitignore rules that we already have in case the path changes at any time.
These were inconsistently linted until a recent commit that moved the
globbing to the config. This is the result of running:
markdownlint-cli2 --fix
Fix linting
chore: Update Flox environment
…nstructions docs(default-environment.md): install to "default" from other dirs
rossturk
approved these changes
Feb 4, 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.