Bump yaml from 2.8.1 to 2.8.3 in /frontend/packages/schema#4071
Open
dependabot[bot] wants to merge 1 commit intomainfrom
Open
Bump yaml from 2.8.1 to 2.8.3 in /frontend/packages/schema#4071dependabot[bot] wants to merge 1 commit intomainfrom
dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps [yaml](https://github.com/eemeli/yaml) from 2.8.1 to 2.8.3. - [Release notes](https://github.com/eemeli/yaml/releases) - [Commits](eemeli/yaml@v2.8.1...v2.8.3) --- updated-dependencies: - dependency-name: yaml dependency-version: 2.8.3 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
dependabot
bot
requested review from
NoritakaIkeda and
sasamuku
and removed request for
a team
dependabot
bot
added
dependencies
|
Finished running flow.
|
||||||||||||
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| "pg-query-emscripten": "5.1.0", | ||
| "valibot": "1.1.0", | ||
| "yaml": "2.8.1", | ||
| "yaml": "2.8.3", |
Contributor
There was a problem hiding this comment.
🔴 Lockfile not updated to match package.json version bump, will break CI
The package.json specifies "yaml": "2.8.3" but pnpm-lock.yaml still records specifier: 2.8.1 and version: 2.8.1 (at pnpm-lock.yaml:978-980). Since CI runs pnpm install --frozen-lockfile (.github/actions/pnpm-setup/action.yml:24), this mismatch will cause the install step to fail with an error about the lockfile being out of date.
Prompt for agents
Run `pnpm install` to regenerate the lockfile so that pnpm-lock.yaml reflects the updated yaml version 2.8.3 specified in frontend/packages/schema/package.json line 26. The lockfile at pnpm-lock.yaml lines 978-980 currently still references yaml 2.8.1. After running pnpm install, commit the updated pnpm-lock.yaml.
Was this helpful? React with 👍 or 👎 to provide feedback.
Check changeset necessityStatus: REQUIRED Reason:
Changeset (copy & paste):---
"@liam-hq/schema": patch
---
- 🐛 Update yaml to 2.8.3 to include upstream bug fixes
- Prevents potential stack overflow during node composition and improves newline handling for empty map values
- Includes new trailingComma formatting option in yaml (no changes to our public API) |
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
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.
Bumps yaml from 2.8.1 to 2.8.3.
Release notes
Sourced from yaml's releases.
Commits
ce145872.8.31e84ebbfix: Catch stack overflow during node composition6b24090ci: Include Prettier check in lint action9424deechore: Refresh lockfiled1aca82Add trailingComma ToString option for multiline flow formatting (#670)4321509ci: Drop the branch filter from GitHub PR actions47207d0chore: Update docs-slate5212faechore: Update docs-slate086fa6b2.8.295f01e9chore: Add funding to package.jsonDependabot 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 commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.