Skip to content

Pin CI packages to specific hashes #51

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 41 commits into from
Aug 25, 2025
Merged

Pin CI packages to specific hashes #51

merged 41 commits into from
Aug 25, 2025

Conversation

janbridley
Copy link
Collaborator

@janbridley janbridley commented Aug 18, 2025

Description

CI has been updated to pin specific hashes of CI scripts, as per the new group standard.

Motivation and Context

Types of Changes

  • Documentation update
  • Bug fix
  • New feature
  • Breaking change1

1The change breaks (or has the potential to break) existing functionality and should be merged into the breaking branch

Checklist:

  • I am familiar with the Development Guidelines
  • The changes introduced by this pull request are covered by existing or newly introduced tests.
  • I have updated the changelog and added my name to the credits.

@janbridley janbridley mentioned this pull request Aug 19, 2025
7 tasks
@janbridley janbridley requested review from Copilot and joaander and removed request for Copilot August 19, 2025 00:08
@janbridley janbridley self-assigned this Aug 19, 2025
@joaander
Copy link
Member

pypa/gh-action-pypi-publish#378 should fix this when merged.

@janbridley janbridley changed the title Pin CI uses to specific hashes Pin CI packages to specific hashes Aug 20, 2025
@janbridley janbridley marked this pull request as ready for review August 25, 2025 13:50
@janbridley janbridley merged commit fc4d1f0 into main Aug 25, 2025
10 checks passed
@janbridley janbridley deleted the chore/ci-pins branch August 25, 2025 14:03
janbridley added a commit that referenced this pull request Aug 25, 2025
<!-- Provide a general summary of your changes in the Title above -->

## Description
Previously, `parsnip` expected a path to a file (provided as either a
str or a pathlib.Path), which was opened into a file buffer in the
__init__ method. This is not optional, and a direct file buffer can now
be provided. We also support raw text blocks (str containing newlines),
which are preprocessed appropriately.
**We make the assumption that all strings that do not point to a file,
do not contain a portion of a valid path, and do not contain the ".cif"
suffix should be treated as CIF data blocks.**

## Motivation and Context

Resolves #49
Blocked by #51 

## Types of Changes
<!-- Please select all items that apply, either now or after creating
the pull request: -->
- [ ] Documentation update
- [ ] Bug fix
- [x] New feature
- [ ] Breaking change<sup>1</sup>

<sup>1</sup>The change breaks (or has the potential to break) existing
functionality and should be merged into the `breaking` branch

## Checklist:
<!-- Please select all items that apply either now or after creating the
pull request. -->
- [x] I am familiar with the [Development
Guidelines](https://github.com/glotzerlab/parsnip/blob/main/doc/source/development.rst)
- [x] The changes introduced by this pull request are covered by
existing or newly introduced tests.
- [x] I have updated the
[changelog](https://github.com/glotzerlab/parsnip/blob/main/ChangeLog.rst)
and added my name to the
[credits](https://github.com/glotzerlab/parsnip/blob/main/doc/source/credits.rst).
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