Version Bump Needed: 1.0.0 → 1.1.0

[ChrisRackauckas-Claude]

Version Bump: 1.0.0 → 1.1.0

Bumping version from 1.0.0 to 1.1.0 to prepare for release.

Changes since v1.0.0 (11 commits)

Precompilation and Imports:

• Fix method overwriting that prevented precompilation (Fix method overwriting that prevented precompilation #137)
• Fix explicit imports for PyCall and Requires

CI/CD Improvements:

• Update CI to test on Julia lts, stable (1), and pre-release (Fix CI failures: typos, docs compat, ExplicitImports compat #138)
• Fix CI failures: typos, docs compat, ExplicitImports compat
• Bump actions/checkout from 4 to 6 (Bump actions/checkout from 4 to 6 #141)

Code Quality:

• Switch from JuliaFormatter to Runic.jl for code formatting (Switch from JuliaFormatter to Runic.jl for code formatting #140)

Registration Command

After merging, register with:

@JuliaRegistrator register

cc @ChrisRackauckas

[JuliaRegistrator]

Error while trying to register: Register Failed
@ChrisRackauckas-Claude, it looks like you are not a publicly listed member/owner in the parent organization (SciML).
If you are a member/owner, you will need to change your membership to public. See GitHub Help

[ChrisRackauckas]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/145715

Recommendation: add release notes

Release notes help your users know what has changed in the new version. For breaking releases in particular, it's recommended to document what breaking changes were made (or point to where changes can be found, such as a changelog).

To add release notes, 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 release notes to this registration, just re-invoke JuliaRegistrator 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.1.0 -m "<description of version>" 689e94a43371199ff0735456dd48e136e6130c72
git push origin v1.1.0