Public Release/26.5.6 (#329)

[Devesh-Skyflow]

• SK-2849: Add v1.x deprecation warning and EOL notic (SK-2849: Add v1.x deprecation warning and EOL notic #327)

• feat(SK-2849): add v1.x deprecation warning and EOL notice

• Print WARN-level deprecation message on Skyflow.init() startup
• Update pom.xml description with EOL date (2026-10-31) and migration guide link

• SK-2837: Add V2.1 migration guide and README upgrade banner (SK-2837: Add V2.1 migration guide and README upgrade banner #313)

• docs: add V2.1 migration guide and README upgrade banner

Adds docs/migrate_to_v2.md covering auth options, client init, request/response structure, error format, and camelCase field name changes for V1 → V2 migration. Adds README banner pointing V1 users to the guide and noting EOL on 2026-10-31.

• docs: update migration guide with v2.1 changes

Add sections for UpdateRequest skyflowId preference, updateLogLevel and getBYOT deprecations.

• docs: add downloadURL→downloadUrl rename to migration guide method renames table

---

• chore: update internal release workflow to trigger on v1/release/* branches

• chore: update internal release trigger to release/v1/* branches

• chore: add workflow_dispatch and upgrade action versions

• [AUTOMATED] Private Release 2.1.0-dev-7a0438b

• chore: skip tests in v1 internal release deploy

• chore: internal release manual-only trigger for v1

• chore: rename internal release workflow for consistency

• chore: restore release/v1/* trigger, remove unintentional tag trigger

• chore: remove manual trigger after merge

• chore: revert workflow changes to v1 baseline

---

• [AUTOMATED] Private Release 2.1.0-dev-202e7ca

• Devesh/sk 2849 v1 deprication (Devesh/sk 2849 v1 deprication #328)

• feat(SK-2849): add v1.x deprecation warning and EOL notice

• Print WARN-level deprecation message on Skyflow.init() startup
• Update pom.xml description with EOL date (2026-10-31) and migration guide link

• SK-2837: Add V2.1 migration guide and README upgrade banner (SK-2837: Add V2.1 migration guide and README upgrade banner #313)

• docs: add V2.1 migration guide and README upgrade banner

Adds docs/migrate_to_v2.md covering auth options, client init, request/response structure, error format, and camelCase field name changes for V1 → V2 migration. Adds README banner pointing V1 users to the guide and noting EOL on 2026-10-31.

• docs: update migration guide with v2.1 changes

Add sections for UpdateRequest skyflowId preference, updateLogLevel and getBYOT deprecations.

• docs: add downloadURL→downloadUrl rename to migration guide method renames table

---

• chore: update internal release workflow to trigger on v1/release/* branches

• chore: update internal release trigger to release/v1/* branches

• chore: add workflow_dispatch and upgrade action versions

• [AUTOMATED] Private Release 2.1.0-dev-7a0438b

• chore: skip tests in v1 internal release deploy

• chore: internal release manual-only trigger for v1

• chore: rename internal release workflow for consistency

• chore: restore release/v1/* trigger, remove unintentional tag trigger

• chore: remove manual trigger after merge

• chore: revert workflow changes to v1 baseline

• fix: fix dead links in README for InsertBulk examples

• chore: upgrade action versions and skip tests for v1 release

• fix: fix sample links in README to point to v1 branch

• fix: fix dead link in migration guide to point to v2 README

• fix: point migration guide link to v1 README vault-apis section

• fix: point migration guide link to main README initialize-the-client section

• docs: add breaking changes summary table to migration guide

---

• [AUTOMATED] Private Release 2.1.0-dev-9ad0ca1

• docs: convert breaking changes table to bullet points in migration guide

• [AUTOMATED] Private Release 2.1.0-dev-4cf2ab8

• fix: version

---

Start with a concise summary of the PR. The first three sections are required. The questions present in each section is there to help you guide you what to add. They are meant to be overwritten by your comments.

Why

• Why are you making the change?
• What is the underlying issue that you are trying to case, in case of fix?
• Why is it needed by the feature you are working on?
• What is the intent behind making the change?

Goal

• What is the intended outcome?
• What part of the feature should start working?
• What are the non-goals or will be covered in future PR?

Testing

• How was the code tested?
• If you haven't written unit tests, why?
• What more testing is needed? Do you intend to manually test it after deployment?
• Do you have any concerns if this changed is released to prod?

Tech debt

• Is the PR adding to tech debt in any way?
• Are you addressing some Tech debt in this PR?
• If both the above are false, feel free to remove this section.