Skip to content

Update dependency org.jspecify:jspecify to v1.0.1 - #1

Merged
NonSwag merged 1 commit into
mainfrom
renovate/org.jspecify-jspecify-1.x
Sep 30, 2026
Merged

NonSwag merged 1 commit into
mainfrom
renovate/org.jspecify-jspecify-1.x

Conversation

@renovate

@renovate renovate Bot commented Sep 30, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
org.jspecify:jspecify (source) 1.0.0 → 1.0.1 age confidence

Warning

Some dependencies could not be looked up. Check the warning logs for more information.


Release Notes

jspecify/jspecify (org.jspecify:jspecify)

v1.0.1: 1.0.1

JSpecify 1.0.1 makes small changes to documentation and build setup but no semantic changes.

Artifacts

Changes since version 1.0.0

  • The JSpecify module-info.class is now present at the root of the jar instead of under a multi-release root. This prevents the jar from containing a file at META-INF/versions/9/OSGI-INF/MANIFEST.MF, which was causing trouble for some users, particularly on Android.
  • The JSpecify module-info.class now contains its version number.
  • We have made various improvements to our Javadoc. While the latest docs are always available at jspecify.dev/docs/api, this release makes our improvements visible in the source files in your IDE.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@NonSwag
NonSwag merged commit 097633d into main Sep 30, 2026
1 check passed
@renovate
renovate Bot deleted the renovate/org.jspecify-jspecify-1.x branch September 30, 2026 17:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant