chore(deps): update dependency jasonetco/create-an-issue to v2.9.1 (.github/workflows/governance.links-checker.yml) (main)#473
Merged
ivankatliarchuk merged 1 commit intoDec 28, 2022
Conversation
…github/workflows/governance.links-checker.yml)
7087732 to
ebcee61
Compare
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 PR contains the following updates:
v2.8.2->v2.9.1v2.8.2->v2.9.1⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the logs for more information.
Release Notes
JasonEtco/create-an-issue
v2.9.1Compare Source
Fixes a regression introduced in #144, where fields that are valid according to GitHub (
nameandabout) were getting flagged as invalid from the changes in #144. See #145/#146 for the fix.v2.9.0Compare Source
This release adds a new step to parsing the issue template, to validate the frontmatter in your template against a defined schema. That way, any missing or invalid fields (like a missing title) will be caught and get a proper error message.
I'm not marking this as a breaking change because the expected schema hasn't changed, now it's just enforcing it. Apologies if this does break anyones templates, but that's a good thing as it'd be pointing out something invalid about it!
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 PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.