Skip to content

Commit

Permalink
add some more limitations, bump version for bugfix release (#47)
Browse files Browse the repository at this point in the history
  • Loading branch information
@ericphanson
ericphanson authored May 17, 2024
1 parent 30f6b47 commit dbc3e05
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 1 deletion.
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 = "ExplicitImports"
uuid = "7d51a73a-1435-4ff3-83d9-f097790105c7"
authors = ["Eric P. Hanson"]
version = "1.4.3"
version = "1.4.4"

[deps]
AbstractTrees = "1520ce14-60c1-5f80-bbc7-55ef81b5835c"
Expand Down
3 changes: 3 additions & 0 deletions README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -86,6 +86,9 @@ These can likely all be fixed by improving the code in `src/get_names_used.jl`,
Known issues:

- `global` and `local` keywords are currently ignored
- `baremodule` is currently not handled
- arguments in macro definitions are not handled (may be treated incorrectly as globals)
- arguments to `let` blocks are not handled (may be treated incorrectly as globals)
- multi-argument `include` calls are ignored
- In Julia, `include` adds the included code at top-level in the module in which it is called. Here, when `include` is called within a local scope, all of the code being included is treated as being within that local scope.
- quoted code (e.g. when building Julia expressions programmatically) may be analyzed incorrectly
Expand Down

2 comments on commit dbc3e05

@ericphanson
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/107091

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 v1.4.4 -m "<description of version>" dbc3e05aa3ba16ca175ff3f600faaf7cbca7a73f
git push origin v1.4.4

Please sign in to comment.