Conversation
tmeijn
pushed a commit
to tmeijn/dotfiles
that referenced
this pull request
Feb 9, 2026
This MR contains the following updates: | Package | Update | Change | |---|---|---| | [jackchuka/mdschema](https://github.com/jackchuka/mdschema) | minor | `v0.9.0` → `v0.11.0` | MR created with the help of [el-capitano/tools/renovate-bot](https://gitlab.com/el-capitano/tools/renovate-bot). **Proposed changes to behavior should be submitted there as MRs.** --- ### Release Notes <details> <summary>jackchuka/mdschema (jackchuka/mdschema)</summary> ### [`v0.11.0`](https://github.com/jackchuka/mdschema/releases/tag/v0.11.0) [Compare Source](jackchuka/mdschema@v0.10.0...v0.11.0) #### What's Changed - feat(rule): link check to include frontmatter links by [@​jackchuka](https://github.com/jackchuka) in [#​41](jackchuka/mdschema#41) **Full Changelog**: <jackchuka/mdschema@v0.10.0...v0.11.0> ### [`v0.10.0`](https://github.com/jackchuka/mdschema/releases/tag/v0.10.0) [Compare Source](jackchuka/mdschema@v0.9.1...v0.10.0) #### What's New **Introduce GitHub Action** #### What's Changed - fix: release tag filter by [@​jackchuka](https://github.com/jackchuka) in [#​39](jackchuka/mdschema#39) - fix: release tag align by [@​jackchuka](https://github.com/jackchuka) in [#​40](jackchuka/mdschema#40) **Full Changelog**: <jackchuka/mdschema@v1...v0.10.0> ### [`v0.9.1`](https://github.com/jackchuka/mdschema/releases/tag/v0.9.1) [Compare Source](jackchuka/mdschema@v0.9.0...v0.9.1) #### What's Changed - feat: generate heading title from literal by [@​takeoverjp](https://github.com/takeoverjp) in [#​37](jackchuka/mdschema#37) #### New Contributors - [@​takeoverjp](https://github.com/takeoverjp) made their first contribution in [#​37](jackchuka/mdschema#37) **Full Changelog**: <jackchuka/mdschema@v0.9.0...v0.9.1> </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this MR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this MR, check this box --- This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0Mi45Ni4wIiwidXBkYXRlZEluVmVyIjoiNDIuOTYuMCIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiUmVub3ZhdGUgQm90IiwiYXV0b21hdGlvbjpib3QtYXV0aG9yZWQiLCJkZXBlbmRlbmN5LXR5cGU6Om1pbm9yIl19-->
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This pull request updates the release workflow, documentation, and action configuration to improve version handling and clarity for the
mdschemaGitHub Action. The main focus is on making the version selection mechanism more intuitive and ensuring the documentation accurately reflects these changes.Improvements to version handling and workflow:
.github/workflows/release.ymlto trigger on all tags starting withv, not just strict semantic versions.Documentation updates:
README.mdto use a specific action version (@v0.9.1) instead of the generic@v1, and clarified theversioninput description to match the new behavior. [1] [2] [3]Action configuration enhancements:
versioninput inaction.ymlto clarify that it defaults to the action ref if not specified, and that setting it tolatestwill always fetch the newest release. The default is now an empty string instead of"latest".action.ymlso that if no version is specified, it uses the action ref (e.g.,@v0.9.1usesv0.9.1), otherwise it uses the specified version or fetches the latest if requested.