Skip to content

Remove legacy compat code in the next major release #1482

Description

@l2ysho

Note

TL;DR — TODO

Candidates

  1. apify upgrade --force — upgrade.ts#L63. Marked [DEPRECATED] and ignored since fix: upgrade command should always check when manually ran #897 (2025-08). Removing it makes -f an unknown-flag error.
  2. apify.json → .actor/actor.json migration — useActorConfig.ts#L92 and the init branch at init.ts#L148. Added in feat: Use .actor/actor.json file (#292) #296 (2022-11). After removal, a project with only apify.json should get a clear error that points to the migration guide.
  3. apify_storage → storage rename — run.ts#L270 and LEGACY_LOCAL_STORAGE_DIR. Added for SDK v3 in chore: update everything to Crawlee, SDK v3 and new template structure #278 (2022-08).

Out of scope

  • v0 → v1 local and telemetry state migrations (2025) — too recent.
  • auth.json and keyring migrations (2026) — still needed.

Done when

  • Each item is removed or explicitly kept, with a reason.
  • MIGRATIONS.md lists the removed behavior.

🤖 Generated with Claude Code

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    t-buildersIssues owned by the Builders team.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions