Skip to content

fix: Improve archive APIs to be able to link archives to actions#2095

Open
tmathern wants to merge 3 commits into
mainfrom
mathern/archive-api
Open

fix: Improve archive APIs to be able to link archives to actions#2095
tmathern wants to merge 3 commits into
mainfrom
mathern/archive-api

Conversation

@tmathern
Copy link
Copy Markdown
Contributor

@tmathern tmathern commented Apr 29, 2026

Changes in this pull request

The recently added archive APIs simplify the handling of ingredient archives, but there is a bug where when those APIs are used, two ingredients can't be linked to actions when a Builder signs (see test scenario test_two_ingredient_archives_link_distinctly_via_actions).

This fixes that.

Checklist

  • This PR represents a single feature, fix, or change.
  • All applicable changes have been documented.
  • Any TO DO items (or similar) have been entered as GitHub issues and the link to that issue has been included in a comment.

@tmathern tmathern self-assigned this Apr 29, 2026
@tmathern tmathern changed the title fix: WIP fix: Improve archive APIs to be able to link archives to actions Apr 29, 2026
@tmathern tmathern requested review from gpeacock and ok-nick April 29, 2026 17:51
@tmathern tmathern marked this pull request as ready for review April 29, 2026 17:51
Comment thread sdk/src/builder.rs
}

let ingredient = reader.to_ingredient()?;
let archive_ingredient_id = reader.active_archive_ingredient_id();
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

we don't know if the saved id came from the label or the instanceId here. We should just save and restore the user assigned label here, and it should be done in reader.to_ingredient.()

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