Skip to content

Conversation

@Amnah199
Copy link
Contributor

@Amnah199 Amnah199 commented Nov 18, 2025

Related Issues

Proposed Changes:

How did you test it?

Updated tests
Locally tested with the example in the issue

Notes for the reviewer

Checklist

  • I have read the contributors guidelines and the code of conduct.
  • I have updated the related issue with new insights and changes.
  • I have added unit tests and updated the docstrings.
  • I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test: and added ! in case the PR includes breaking changes.
  • I have documented my code.
  • I have added a release note file, following the contributors guidelines.
  • I have run pre-commit hooks and fixed any issue.

@vercel
Copy link

vercel bot commented Nov 18, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Preview Comments Updated (UTC)
haystack-docs Ignored Ignored Preview Dec 1, 2025 2:46pm

@Amnah199 Amnah199 added the ignore-for-release-notes PRs with this flag won't be included in the release notes. label Nov 18, 2025
@Amnah199 Amnah199 removed the ignore-for-release-notes PRs with this flag won't be included in the release notes. label Nov 19, 2025
@Amnah199 Amnah199 marked this pull request as ready for review November 19, 2025 09:31
@Amnah199 Amnah199 requested a review from a team as a code owner November 19, 2025 09:31
@Amnah199 Amnah199 requested review from anakin87 and removed request for a team November 19, 2025 09:31
@anakin87 anakin87 requested a review from sjrl November 19, 2025 09:41
@sjrl
Copy link
Contributor

sjrl commented Nov 19, 2025

@Amnah199 this is technically a breaking change b/c existing pipeline snapshots would no longer be loadable right?

@Amnah199
Copy link
Contributor Author

Amnah199 commented Nov 20, 2025

@sjrl you are right! Its a breaking change. Do you think I should try to make it backward compatible and log a warning before we decide to remove that support in next releases?

@anakin87
Copy link
Member

Not an expert on this topic, but I'll try to review...
Feel free to involve David if you think he has a better background.

@Amnah199 let's make it backward compatible (if possible) and add tests to show existing pipeline snapshots are still loadable.

@github-actions github-actions bot added the type:documentation Improvements on the docs label Dec 1, 2025
@coveralls
Copy link
Collaborator

coveralls commented Dec 1, 2025

Pull Request Test Coverage Report for Build 19826642961

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 47 unchanged lines in 6 files lost coverage.
  • Overall coverage increased (+0.7%) to 92.16%

Files with Coverage Reduction New Missed Lines %
dataclasses/chat_message.py 1 99.35%
tracing/datadog.py 1 97.83%
core/pipeline/async_pipeline.py 3 65.88%
core/pipeline/breakpoint.py 8 88.59%
core/pipeline/pipeline.py 8 91.74%
components/fetchers/link_content.py 26 86.1%
Totals Coverage Status
Change from base Build 19500014393: 0.7%
Covered Lines: 14035
Relevant Lines: 15229

💛 - Coveralls

Copy link
Contributor

@sjrl sjrl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

@Amnah199 Amnah199 merged commit 050c25c into main Dec 1, 2025
21 checks passed
@Amnah199 Amnah199 deleted the serialize-pipleine-outputs branch December 1, 2025 15:01
GunaPalanivel added a commit to GunaPalanivel/haystack that referenced this pull request Dec 15, 2025
Remove temporary deserialization logic for old pipeline_outputs format in
pipeline snapshots. This backward-compatibility layer was introduced in
PR deepset-ai#10096 and marked for removal in Haystack 2.23.0.

BREAKING CHANGE: Pipeline snapshots created before Haystack 2.17.0 will
no longer deserialize correctly. Users must recreate snapshots with the
current Haystack version or manually migrate to the new serialization schema.

Changes:
- Remove conditional deserialization check in Pipeline.run()
- Remove test_load_pipeline_snapshot_with_old_pipeline_outputs_format test
- Add breaking change documentation with migration instructions

The new format uses 'serialization_schema' and 'serialized_data' fields,
consistent with other pipeline state serialization.

Closes deepset-ai#10168
Ref deepset-ai#10096
GunaPalanivel added a commit to GunaPalanivel/haystack that referenced this pull request Jan 13, 2026
Remove temporary deserialization logic for old pipeline_outputs format in
pipeline snapshots. This backward-compatibility layer was introduced in
PR deepset-ai#10096 and marked for removal in Haystack 2.23.0.

BREAKING CHANGE: Pipeline snapshots created before Haystack 2.17.0 will
no longer deserialize correctly. Users must recreate snapshots with the
current Haystack version or manually migrate to the new serialization schema.

Changes:
- Remove conditional deserialization check in Pipeline.run()
- Remove test_load_pipeline_snapshot_with_old_pipeline_outputs_format test
- Add breaking change documentation with migration instructions

The new format uses 'serialization_schema' and 'serialized_data' fields,
consistent with other pipeline state serialization.

Closes deepset-ai#10168
Ref deepset-ai#10096
anakin87 added a commit that referenced this pull request Jan 14, 2026
…at (#10249)

Remove temporary deserialization logic for old pipeline_outputs format in
pipeline snapshots. This backward-compatibility layer was introduced in
PR #10096 and marked for removal in Haystack 2.23.0.

BREAKING CHANGE: Pipeline snapshots created before Haystack 2.17.0 will
no longer deserialize correctly. Users must recreate snapshots with the
current Haystack version or manually migrate to the new serialization schema.

Changes:
- Remove conditional deserialization check in Pipeline.run()
- Remove test_load_pipeline_snapshot_with_old_pipeline_outputs_format test
- Add breaking change documentation with migration instructions

The new format uses 'serialization_schema' and 'serialized_data' fields,
consistent with other pipeline state serialization.

Closes #10168
Ref #10096

Co-authored-by: Stefano Fiorucci <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Missing serialization of pipeline_outputs when creating a PipelineSnapshot

5 participants