Skip to content

chore(deps): dependency sweep — pnpm security fix + lockfile freshening - #2938

Merged
B4nan merged 1 commit into
masterfrom
chore/deps-sweep
Sep 2, 2026
Merged

B4nan merged 1 commit into
masterfrom
chore/deps-sweep

Conversation

@apify-deps

@apify-deps apify-deps Bot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Summary

Dependency sweep — security bump + in-range freshening (all within existing ranges):

  • pnpm (self-managed toolchain, pnpm-lock.yaml) 11.9.0 → 11.25.0 (high — was < 11.11.0)
  • in-range refresh across the root and apify-docs-theme workspace projects (@apify/ui-icons, @apify/ui-library, algoliasearch, algoliasearch-helper, babel-loader, postcss-preset-env, react-hotkeys-hook, @stoplight/spectral-cli, and transitive/peer bumps)
  • denied the install script for the newly-pulled-in @scarf/scarf (telemetry beacon, no functional need) in pnpm-workspace.yaml's allowBuilds

🧹 Pruned overrides (no longer needed)

  • @stoplight/spectral-core>minimatch — no-op: resolves to the same 3.1.5 with or without it.
  • @stoplight/spectral-ruleset-bundler>rollup — no-op: resolves to the same 2.80.0 with or without it.
  • postcss — no-op: everything already converges to 8.5.26 without it.
  • protobufjs — the package is gone from the tree entirely.
  • dompurify — no-op: resolves to the same 3.4.14 with or without it.
  • fast-xml-parser — the package is gone from the tree entirely.
  • ajv@>=8.0.0 <9.0.0 — no-op: the 8.x line already resolves to 8.18.0 without it.

Kept js-yaml (two entries), yaml@1, lodash, and the serialize-javascript pair — removing any of those still changes the resolved version, so they're still doing a job.

🤖 Generated with Claude Code

Bumps the self-managed pnpm toolchain past the patched floor for a high
severity Dependabot alert, refreshes in-range deps across both workspace
projects, denies the newly-introduced @scarf/scarf install script, and
prunes overrides that no longer do anything.
@apify-deps apify-deps Bot added the adhoc Ad-hoc unplanned task added during the sprint. label Sep 2, 2026
@apify-deps
apify-deps Bot requested a review from B4nan September 2, 2026 01:09
@apify-service-account

apify-service-account commented Sep 2, 2026 •

Copy link
Copy Markdown
Contributor

🗑️ Preview for this PR was deleted.

@B4nan
B4nan merged commit bbb71a1 into master Sep 2, 2026
14 checks passed
@B4nan
B4nan deleted the chore/deps-sweep branch September 2, 2026 09:08
vdusek added a commit to apify/apify-client-python that referenced this pull request Sep 3, 2026
Regenerates the models from the [published OpenAPI
specification](https://docs.apify.com/api/openapi.json), version
`v2-2026-08-30T172245Z` -> `v2-2026-08-31T125154Z` (the stamp lags its
content by one deploy; the content is from 2026-09-02).

- Adds the `description` field to `Task`, `CreateTaskRequest`, and
`UpdateTaskRequest` (apify/apify-docs#2922).
- Sets `collapse_root_models_name_strategy = "child"` for
datamodel-codegen. apify/apify-docs#2938 bumped `@redocly/cli` 2.26.0 ->
2.49.0, and its bundler now keeps the shared `RequestMethod` alias (a
`$ref` to `HttpMethod` plus a description) as a separate component
instead of collapsing it. datamodel-codegen turned that into a
`RequestMethod(RootModel[HttpMethod])` wrapper, so `request.method` no
longer compared equal to plain strings and the request queue integration
tests failed. With the option the alias folds back into `HttpMethod`,
and the generated models are identical to the previous bundler's output.

> Generated by the [Regenerate
models](https://github.com/apify/apify-client-python/actions/workflows/on_schedule_regenerate_models.yaml)
workflow.

*✍️ Drafted by Claude Code*

---------

Co-authored-by: Vlada Dusek <v.dusek96@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

adhoc Ad-hoc unplanned task added during the sprint.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants