Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Merge 0.3.0 release process changes back into master #893

Merged
merged 7 commits into from
Oct 16, 2024
Merged

Merge 0.3.0 release process changes back into master #893

merged 7 commits into from
Oct 16, 2024

Commits on Oct 15, 2024

  1. Bump to version 0.3.0.

    @robertbartel
    robertbartel committed Oct 15, 2024
    Configuration menu
    Copy the full SHA
    7df5166 View commit details
    Browse the repository at this point in the history

  2. Run test/validate on release branches.

    @robertbartel
    robertbartel committed Oct 15, 2024
    Configuration menu
    Copy the full SHA
    f8d72e6 View commit details
    Browse the repository at this point in the history

  3. Apply other Actions to release branches. 

    Applying other Github Actions that run against the master branch to
release branches also.
    @robertbartel
    robertbartel committed Oct 15, 2024
    Configuration menu
    Copy the full SHA
    5570381 View commit details
    Browse the repository at this point in the history

  4. Update Actions to install 1.x numpy. 

    Updating Actions depending on numpy install to use pre-2.0 numpy version
as is currently required for ngen builds.
    @robertbartel @aaraney
    robertbartel authored and aaraney committed Oct 15, 2024
    Configuration menu
    Copy the full SHA
    f3599c1 View commit details
    Browse the repository at this point in the history

  5. Fix Action to strictly require numpy < 2.0.

    @robertbartel @aaraney
    robertbartel authored and aaraney committed Oct 15, 2024
    Configuration menu
    Copy the full SHA
    7480968 View commit details
    Browse the repository at this point in the history

  6. Change Action numpy fix to use constraints. 

    Using pip constraints to ensure any downstream
`input.additional_python_requirements` that may be installed also are
prevented from installing a problematic version.
    @robertbartel @aaraney
    robertbartel authored and aaraney committed Oct 15, 2024
    Configuration menu
    Copy the full SHA
    7fdb524 View commit details
    Browse the repository at this point in the history

  7. Fix placement of constraints.txt in Action. 

    Cannot move to / due to read-only file system; instead, use
$GITHUB_WORKSPACE in order to be able to specify absolute path to file
in PIP_CONSTRAINT.
    @robertbartel
    robertbartel committed Oct 15, 2024
    Configuration menu
    Copy the full SHA
    e51cc62 View commit details
    Browse the repository at this point in the history