Skip to content

Commit

Permalink
version 0.9.2
Browse files Browse the repository at this point in the history
  • Loading branch information
@aviatesk
aviatesk committed May 22, 2024
1 parent b943e09 commit 8652a97
Show file tree
Hide file tree
Showing 2 changed files with 11 additions and 3 deletions.
12 changes: 10 additions & 2 deletions CHANGELOG.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,13 @@ All notable changes to this project will be documented in this file.
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).

## [0.9.2]

### Fixed

- Allow overly deep relative module paths when analyzing a package with `report_package`
(aviatesk/JET.jl#619, aviatesk/JET.jl#633)

## [0.9.1]

### Fixed
Expand All @@ -18,7 +25,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

- A new configuration `stacktrace_types_limit::Union{Nothing,Int}=nothing` has been added.
It's turned on by default and limits deeply nested types when JET prints reports.
If you prefer the old behavior, set `stacktrace_types_limit=0`.
If you prefer the old behavior, set `stacktrace_types_limit=0` (aviatesk/JET.jl#601).

### Changed

Expand Down Expand Up @@ -245,7 +252,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
<!-- links -->
[unreleased]: https://github.com/aviatesk/JET.jl/compare/v0.9.1...HEAD
[unreleased]: https://github.com/aviatesk/JET.jl/compare/v0.9.2...HEAD
[0.9.1]: https://github.com/aviatesk/JET.jl/compare/v0.9.1...v0.9.2
[0.9.1]: https://github.com/aviatesk/JET.jl/compare/v0.9.0...v0.9.1
[0.9.0]: https://github.com/aviatesk/JET.jl/compare/v0.8.29...v0.9.0
[0.8.9]: https://github.com/aviatesk/JET.jl/compare/v0.8.8...v0.8.9
Expand Down
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 <aviatesk@gmail.com>"]
version = "0.9.1"
version = "0.9.2"

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

2 comments on commit 8652a97

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

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.2 -m "<description of version>" 8652a97a61dfd756cfbedd32a16bcaba30d7d1af
git push origin v0.9.2

Please sign in to comment.