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

Update the changelog for a new version (v2.3.2) #1286

Merged
merged 1 commit into from
Apr 11, 2023
Merged

Update the changelog for a new version (v2.3.2) #1286

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,9 @@
All notable changes to this project will be documented in this file.

## [Unreleased]

## [2.3.2] - 2023-04-10

### Added
- The `catalog_name` keyword has been added to the `UVData.read` and `UVData.select`
methods to allow users to select on source name.
Expand Down
8 changes: 5 additions & 3 deletions docs/references/making_release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,12 +41,14 @@ To do it fully by hand:

1. Fork the feedstock repo to your personal github account.
2. Make a new branch on your fork for the changes
3. get the new SHA from pypi: Go to the PyPI file listing page, next to each
file there's a little link labeled SHA256 that will copy the right value to your
3. get the new SHA from pypi: Go to the PyPI download page for this release. Next to the
source distribution (.tar.gz file) there's a "view hashes" link. Click that link to see
the SHA256 hash and click the "copy" link next to it to copy the right value to your
clipboard. Or you can just download the file yourself and run `openssl sha256` on it.
4. update recipe/meta.yaml: minimally update the version, build & SHA (if it’s
a new version, reset the build to zero, otherwise bump the build number).
Generally review the whole file for things that should change.
Generally review the whole file for things that should change, particularly any
dependency changes.
5. push your branch to github
6. open a PR against the feedstock repo from your branch.
7. get a bot to automatically re-render the code by commenting on the PR with
Expand Down