Skip to content

Commit

Permalink
Loading
Loading status checks…
version 0.9.6
Browse files Browse the repository at this point in the history
@aviatesk
aviatesk committed Jul 3, 2024

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode
1 parent 447c7a3 commit 3d8adb6
Showing 2 changed files with 7 additions and 1 deletion.
6 changes: 6 additions & 0 deletions CHANGELOG.md
View file
Original file line number Diff line number Diff line change
@@ -6,6 +6,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

<!-- links start -->
[0.9.6]: https://github.com/aviatesk/JET.jl/compare/v0.9.5...v0.9.6
[0.9.5]: https://github.com/aviatesk/JET.jl/compare/v0.9.4...v0.9.5
[0.9.4]: https://github.com/aviatesk/JET.jl/compare/v0.9.3...v0.9.4
[0.9.3]: https://github.com/aviatesk/JET.jl/compare/v0.9.2...v0.9.3
@@ -24,6 +25,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
[0.8.0]: https://github.com/aviatesk/JET.jl/compare/v0.7.15...v0.8.0
<!-- links end -->

## [0.9.6]
### Fixed
- `report_opt` no longer raises reports from callees on `throw` code path when the
`skip_unoptimized_throw_blocks::Bool=true` configuration is enabled (aviatesk/JET.jl#643).

## [0.9.5]
### Added
- `analyze_from_definitions` can now be specified as `entry_point_name::Symbol` to make
2 changes: 1 addition & 1 deletion Project.toml
View file
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
name = "JET"
uuid = "c3a54625-cd67-489e-a8e7-0a5a0ff4e31b"
authors = ["Shuhei Kadowaki <[email protected]>"]
version = "0.9.5"
version = "0.9.6"

[deps]
CodeTracking = "da1fd8a2-8d9e-5ec2-8556-3022fb5608a2"

2 comments on commit 3d8adb6

@aviatesk
Copy link
Owner Author

Choose a reason for hiding this comment

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

@JuliaRegistrator register

@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/110313

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.9.6 -m "<description of version>" 3d8adb657da83b4e0426c8dd766e10a68529821a
git push origin v0.9.6

Please sign in to comment.