Repository navigation
build: pin FAST-HEP dependencies exactly - #7
Merged
Merged
Conversation
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Part of a workspace-wide rollout (see
FAST-HEP/fasthep-dev, task2026-10-26-package-docs-rollout): as the last package in the release order, workshop's dependencies should be pinned exactly rather than floor-pinned, so a workshop release always builds against the exact versions it was tested with.fasthep-dev'sscripts/release/update_versions.py(from the already-merged2026-10-26-release-tooling-overhaultask) now also rewrites these pins automatically at release time — this PR only fixes the current operator, not the version numbers, which the release tooling will bump going forward.Independent of, and does not depend on, the sibling
docs/changelog-and-policybranch/PR — kept separate since this is a behavioural change, not a docs one.Evidence
Before:
fasthep-flow = {version = ">=2026.08.3"}and six more>=-pinned FAST-HEP dependencies.After: same six packages, same version numbers,
==instead of>=; table form preserved forfasthep-flow, bare-string form for the rest, exactly as before. Verified withfasthep-dev's ownscripts/release/release_data.py::validate_workshop_pinsrun against this file — returns[](clean).Merge Danger
Low: a pin-operator change in a non-published, example/tutorial repository. The only behavioural effect is that
pixi installwill now refuse to resolve if a listed FAST-HEP package's exact version isn't available (instead of silently picking up a newer one) — this is the intended tightening.AI-assisted contributions
This PR's content was generated by Claude (Sonnet 5), orchestrated by @kreczko across a multi-session workspace effort. What was AI-generated: identifying the operator-only change needed and applying it, then verifying with the release-tooling repo's own validator. What was reviewed: the repository owner read and approved the diff before pushing (this workspace's standard two-gate review: push, then PR). No known limitations — this is a mechanical, fully-verified change.
🤖 Generated with Claude Code