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.

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

Add GHA release workflow #3122

Closed
wants to merge 32 commits into from
Closed

Add GHA release workflow #3122

wants to merge 32 commits into from

Conversation

zaneselvans
Copy link
Member

@zaneselvans zaneselvans commented Dec 5, 2023

PR Overview

Add a GitHub Actions Workflow that will coordinate the production of data & software releases, whenever a date-style version tag starting with v20 is pushed. We need to create GitHub releases to trigger the Zenodo software archiving, and may or may not want to push the same release to PyPI for consistency.

Other workflows can be set to kick off on: release or with the same tagging criteria, to:

  • run a tagged build
  • publish the results to GCS, S3, and Zenodo

PR Checklist

  • Merge the most recent version of the branch you are merging into (probably dev).
  • All CI checks are passing. Run tests locally to debug failures
  • Make sure you've included good docstrings.
  • For major data coverage & analysis changes, run data validation tests
  • Include unit tests for new functions and classes.
  • Defensive data quality/sanity checks in analyses & data processing functions.
  • Update the release notes and reference reference the PR and related issues.
  • Do your own explanatory review of the PR to help the reviewer understand what's going on and identify issues preemptively.

aesharpe and others added 30 commits November 30, 2023 15:15
…ssions-control

Extract EIA923 emissions control table and add 2022 final release dat…
Sort DBs Fly Datasette; don't distribute Datasette's metadata.yml
… via cli flag (#2895)

This introduces `--dagster-workers` flag for both `pudl_etl` and `ferc_to_sqlite` scripts. Based on the value, we will either use number of multiprocess workers equal to available CPUs (default), single in-process worker (1) or number of multiprocess workers capped by arbitrary positive number.

This doesn't change default behavior, which is to use number of multiprocess dagster workers equal to number of available CPUs.
Improve flexibility for publishing options

Merging this in today so we can see how it goes with tonight's build, and so I can integrate the changes with #3086.
Bumps [google-github-actions/auth](https://github.com/google-github-actions/auth) from 1 to 2.
- [Release notes](https://github.com/google-github-actions/auth/releases)
- [Changelog](https://github.com/google-github-actions/auth/blob/main/CHANGELOG.md)
- [Commits](google-github-actions/auth@v1...v2)

---
updated-dependencies:
- dependency-name: google-github-actions/auth
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
Bumps [actions/checkout](https://github.com/actions/checkout) from 3 to 4.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@v3...v4)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
…actions/dev/actions/checkout-4

Bump actions/checkout from 3 to 4
…actions/dev/google-github-actions/auth-2

Bump google-github-actions/auth from 1 to 2
Bumps [docker/login-action](https://github.com/docker/login-action) from 2.1.0 to 3.0.0.
- [Release notes](https://github.com/docker/login-action/releases)
- [Commits](docker/login-action@v2.1.0...v3.0.0)

---
updated-dependencies:
- dependency-name: docker/login-action
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 4.0.0 to 5.1.0.
- [Release notes](https://github.com/docker/build-push-action/releases)
- [Commits](docker/build-push-action@v4.0.0...v5.1.0)

---
updated-dependencies:
- dependency-name: docker/build-push-action
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
Bumps [docker/setup-buildx-action](https://github.com/docker/setup-buildx-action) from 2.5.0 to 3.0.0.
- [Release notes](https://github.com/docker/setup-buildx-action/releases)
- [Commits](docker/setup-buildx-action@v2.5.0...v3.0.0)

---
updated-dependencies:
- dependency-name: docker/setup-buildx-action
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
…actions/dev/docker/build-push-action-5.1.0

Bump docker/build-push-action from 4.0.0 to 5.1.0
…actions/dev/docker/setup-buildx-action-3.0.0

Bump docker/setup-buildx-action from 2.5.0 to 3.0.0
…actions/dev/docker/login-action-3.0.0

Bump docker/login-action from 2.1.0 to 3.0.0
* Hide diffs in lock files by default.

* Add mypy as a test for lockfile diff visibility. pudl-bot, do your thing!

* Update conda-lock.yml and rendered conda environment files.

* Revert "Add mypy as a test for lockfile diff visibility. pudl-bot, do your thing!"

This reverts commit e7a8e82.

* Update conda-lock.yml and rendered conda environment files.

---------

Co-authored-by: jdangerx <[email protected]>
@zaneselvans zaneselvans linked an issue Dec 5, 2023 that may be closed by this pull request
@zaneselvans zaneselvans added the release Tasks directly related to data and software releases. label Dec 5, 2023
@zaneselvans zaneselvans self-assigned this Dec 5, 2023
@zaneselvans zaneselvans changed the base branch from dev to main December 5, 2023 16:17
@zaneselvans zaneselvans closed this Dec 5, 2023
@zaneselvans zaneselvans deleted the gha-release-workflow branch December 5, 2023 16:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release Tasks directly related to data and software releases.
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

4 participants