Skip to content

Commit

Permalink
bump version
Browse files Browse the repository at this point in the history
  • Loading branch information
ajwheeler authored Jan 2, 2025
1 parent 38990bd commit 5eb4925
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion Project.toml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
name = "Korg"
uuid = "acafc109-a718-429c-b0e5-afd7f8c7ae46"
authors = ["Adam Wheeler <adamwhlr@gmail.com>", "Matthew Abruzzo <matthewabruzzo@gmail.com>"]
version = "0.41.1"
version = "0.42.0"

This comment has been minimized.

Copy link
@ajwheeler

ajwheeler Jan 2, 2025

Author Owner

This comment has been minimized.

Copy link
@ajwheeler

ajwheeler Jan 2, 2025

Author Owner

@JuliaRegistrator register

Release notes:

Features

  • Korg now has it's own linelist format (just HDF5), which can be written with Korg.save_linelist (fields are well-documented). These files can be read like any other linelist with Korg.read_linelist. (#389)
  • There is now experimental support for loading in ExoMol linelists with Korg.load_ExoMol_linelist (#385 #390).

Notable changes

  • a warning displayed with synthesizing in the APOGEE wavelength region with MHD on for hydrogen lines. (#388)

This comment has been minimized.

Copy link
@ajwheeler

ajwheeler Jan 3, 2025

Author Owner

@JuliaRegistrator register

Release notes:

Breaking Changes

  • none

Features

  • Korg now has it's own linelist format (just HDF5), which can be written with Korg.save_linelist (fields are well-documented). These files can be read like any other linelist with Korg.read_linelist. (#389)
  • There is now experimental support for loading in ExoMol linelists with Korg.load_ExoMol_linelist (#385 #390).

Notable changes

  • a warning displayed with synthesizing in the APOGEE wavelength region with MHD on for hydrogen lines. (#388)

[deps]
CSV = "336ed68f-0bac-5ca0-87d4-7b16caf5d00b"
Expand Down

3 comments on commit 5eb4925

@JuliaRegistrator
Copy link

Choose a reason for hiding this comment

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

Registration pull request created: JuliaRegistries/General/122314

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.42.0 -m "<description of version>" 5eb4925cded638443c8c73055cbad10e4bcd597b
git push origin v0.42.0

@JuliaRegistrator
Copy link

Choose a reason for hiding this comment

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

Registration pull request updated: JuliaRegistries/General/122314

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.42.0 -m "<description of version>" 5eb4925cded638443c8c73055cbad10e4bcd597b
git push origin v0.42.0

@JuliaRegistrator
Copy link

Choose a reason for hiding this comment

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

Registration pull request updated: JuliaRegistries/General/122314

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.42.0 -m "<description of version>" 5eb4925cded638443c8c73055cbad10e4bcd597b
git push origin v0.42.0

Please sign in to comment.