Skip to content

Conversation

@nabobalis
Copy link
Member

@nabobalis nabobalis commented Dec 3, 2025

Updated spec0 file from the specs repo

Added the action to do a release of the schedule in a machine readable format from https://github.com/savente93/spec0-schedule

Added some tests with only setuptools pyproject toml files.

@nabobalis nabobalis changed the title test ci on actions Rando changes Dec 3, 2025
@nabobalis nabobalis changed the title Rando changes Minor Updates Dec 3, 2025
@nabobalis nabobalis marked this pull request as ready for review December 3, 2025 19:13
@nabobalis
Copy link
Member Author

nabobalis commented Dec 3, 2025

Testing downstream via https://github.com/LM-SAL/aiapy/actions/workflows/update-spec0.yaml

Finally got it to open: LM-SAL/aiapy#377

@nabobalis
Copy link
Member Author

TODO: Replace the download location to use this repo in the future.

@nabobalis nabobalis enabled auto-merge December 3, 2025 20:51
@nabobalis nabobalis disabled auto-merge December 3, 2025 20:51
@nabobalis nabobalis merged commit 870132e into main Dec 3, 2025
2 checks passed
@nabobalis nabobalis deleted the ci branch December 3, 2025 20:51
Copy link
Member

@bsipocz bsipocz left a comment

Choose a reason for hiding this comment

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

This is water under the bridge, but I think these should be fixed up in follow-up PR(s) and then tagging new releases.

fi
- name: Fetch Schedule from release
uses: robinraju/[email protected]
Copy link
Member

Choose a reason for hiding this comment

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

Definitely for the third party actions please use the hashes, but maybe to be consistent do it for everything.

Copy link
Member Author

Choose a reason for hiding this comment

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

Will update

- name: Fetch Schedule from release
uses: robinraju/[email protected]
with:
repository: "savente93/SPEC0-schedule"
Copy link
Member

Choose a reason for hiding this comment

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

we should not rely on a third party location for any SPEC0 related content

Copy link
Member Author

Choose a reason for hiding this comment

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

I agree but I need to get the release working on this repo first. Or even if we want to do it in this repo or a separate repo.

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.

3 participants