Skip to content

Conversation

@jasonyuezhang
Copy link
Owner

Bumps qs from 6.13.1 to 6.14.1.

Changelog

Sourced from qs's changelog.

6.14.1

  • [Fix] ensure arrayLength applies to [] notation as well
  • [Fix] parse: when a custom decoder returns null for a key, ignore that key
  • [Refactor] parse: extract key segment splitting helper
  • [meta] add threat model
  • [actions] add workflow permissions
  • [Tests] stringify: increase coverage
  • [Dev Deps] update eslint, @ljharb/eslint-config, npmignore, es-value-fixtures, for-each, object-inspect

6.14.0

  • [New] parse: add throwOnParameterLimitExceeded option (#517)
  • [Refactor] parse: use utils.combine more
  • [patch] parse: add explicit throwOnLimitExceeded default
  • [actions] use shared action; re-add finishers
  • [meta] Fix changelog formatting bug
  • [Deps] update side-channel
  • [Dev Deps] update es-value-fixtures, has-bigints, has-proto, has-symbols
  • [Tests] increase coverage
Commits
  • 3fa11a5 v6.14.1
  • a626704 [Dev Deps] update npmignore
  • 3086902 [Fix] ensure arrayLength applies to [] notation as well
  • fc7930e [Dev Deps] update eslint, @ljharb/eslint-config
  • 0b06aac [Dev Deps] update @ljharb/eslint-config
  • 64951f6 [Refactor] parse: extract key segment splitting helper
  • e1bd259 [Dev Deps] update @ljharb/eslint-config
  • f4b3d39 [eslint] add eslint 9 optional peer dep
  • 6e94d95 [Dev Deps] update eslint, @ljharb/eslint-config, npmignore
  • 973dc3c [actions] add workflow permissions
  • Additional commits viewable in compare view

Dependabot compatibility score

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 commands and options

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 this major version will 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 version will 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 dependency will 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.

Copied from getsentry#105590
Original PR: getsentry#105590

Bumps [qs](https://github.com/ljharb/qs) from 6.13.1 to 6.14.1.
- [Changelog](https://github.com/ljharb/qs/blob/main/CHANGELOG.md)
- [Commits](ljharb/qs@v6.13.1...v6.14.1)

---
updated-dependencies:
- dependency-name: qs
  dependency-version: 6.14.1
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
@propel-test-bot
Copy link

propel-test-bot bot commented Jan 1, 2026

🚨 GitHub App authentication failed due to missing appId configuration on commit 40791d9.

Why it failed

  • The getsentry/action-github-app-token action requires an appId parameter that is not provided
  • Error: [@octokit/auth-app] appId option is required at line 2026-01-01T22:09:37.0205735Z
  • This is a workflow configuration issue, not related to the qs dependency bump in api-docs/pnpm-lock.yaml

Fix it

  • Add the missing appId input to getsentry/action-github-app-token step in .github/workflows/getsentry-dispatcher.yml
  • Ensure GETSENTRY_APP_ID or equivalent secret is configured in repository settings
  • Verify app-private-key secret is also properly set for the GitHub App token action

Follow up

  • Check if this workflow runs successfully on the main sentry/sentry repo vs this fork
  • Confirm all required GitHub App secrets are available in jasonyuezhang/sentry repository settings
Workflow details
2026-01-01T22:09:27.4129830Z Current runner version: '2.330.0'
2026-01-01T22:09:27.4163191Z ##[group]Runner Image Provisioner
2026-01-01T22:09:27.4164569Z Hosted Compute Agent
2026-01-01T22:09:27.4165424Z Version: 20251211.462
2026-01-01T22:09:27.4166503Z Commit: 6cbad8c2bb55d58165063d031ccabf57e2d2db61
2026-01-01T22:09:27.4167628Z Build Date: 2025-12-11T16:28:49Z
2026-01-01T22:09:27.4168657Z Worker ID: {b070bf2c-ba9d-47a6-8037-c87a197c59f1}
2026-01-01T22:09:27.4169775Z ##[endgroup]
2026-01-01T22:09:27.4170691Z ##[group]Operating System
2026-01-01T22:09:27.4171531Z Ubuntu
2026-01-01T22:09:27.4172336Z 24.04.3
2026-01-01T22:09:27.4173028Z LTS
2026-01-01T22:09:27.4173771Z ##[endgroup]
2026-01-01T22:09:27.4174847Z ##[group]Runner Image
2026-01-01T22:09:27.4175798Z Image: ubuntu-24.04
2026-01-01T22:09:27.4176623Z Version: 20251215.174.1
2026-01-01T22:09:27.4178379Z Included Software: https://github.com/actions/runner-images/blob/ubuntu24/20251215.174/images/ubuntu/Ubuntu2404-Readme.md
2026-01-01T22:09:27.4181066Z Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu24%2F20251215.174
2026-01-01T22:09:27.4182800Z ##[endgroup]
2026-01-01T22:09:27.4184779Z ##[group]GITHUB_TOKEN Permissions
2026-01-01T22:09:27.4187376Z Contents: read
2026-01-01T22:09:27.4188179Z Metadata: read
2026-01-01T22:09:27.4189062Z PullRequests: write
2026-01-01T22:09:27.4189890Z ##[endgroup]
2026-01-01T22:09:27.4192859Z Secret source: Actions
2026-01-01T22:09:27.4193906Z Prepare workflow directory
2026-01-01T22:09:27.4659002Z Prepare all required actions
2026-01-01T22:09:27.4715537Z G…

View the failing check

@propel-test-bot
Copy link

Update js-yaml patch versions in api-docs pnpm lockfile

This PR updates js-yaml patch versions referenced in api-docs/pnpm-lock.yaml, ensuring the lockfile reflects js-yaml 3.14.2 and 4.1.1 where previously 3.14.1 and 4.1.0 were used. Despite the PR title and commit message referencing a qs bump to 6.14.1, the lockfile still pins qs at 6.13.1 in both packages and snapshots sections.

Key Changes

• Root importer . in api-docs/pnpm-lock.yaml now resolves js-yaml version 3.14.2 instead of 3.14.1 while keeping the specifier ^3.14.0.
• The packages section replaces entries [email protected] and [email protected] with [email protected] and [email protected], including updated resolution.integrity hashes.
• Snapshot dependencies are updated so @apidevtools/[email protected] now depends on js-yaml: 4.1.1 (was 4.1.0) and [email protected] now depends on js-yaml: 3.14.2 (was 3.14.1).
qs remains at 6.13.1 in both the packages and snapshots sections, so the intended bump to 6.14.1 described in the PR body is not reflected in this lockfile.

Affected Areas

• api-docs dependency resolution via api-docs/pnpm-lock.yaml
• Tooling and libraries that consume js-yaml within the api-docs workspace (e.g., json-refs, @apidevtools/json-schema-ref-parser)

This summary was automatically generated by @propel-code-bot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants