Repository navigation
Commit 4a570b2
authored
Bump org.jspecify:jspecify from 1.0.0 to 1.0.1 (#509)
Bumps [org.jspecify:jspecify](https://github.com/jspecify/jspecify) from
1.0.0 to 1.0.1.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/jspecify/jspecify/releases">org.jspecify:jspecify's
releases</a>.</em></p>
<blockquote>
<h2>1.0.1</h2>
<p>JSpecify 1.0.1 makes small changes to documentation and build setup
but no semantic changes.</p>
<h1>Artifacts</h1>
<ul>
<li><a href="https://jspecify.dev/docs/api/">Javadoc</a></li>
<li>Maven Central: <a
href="https://repo.maven.apache.org/maven2/org/jspecify/jspecify/1.0.1/">org.jspecify:jspecify</a></li>
</ul>
<h1>Changes since version 1.0.0</h1>
<ul>
<li>The JSpecify <code>module-info.class</code> is now present at the
root of the jar instead of under <a
href="https://openjdk.org/jeps/238">a multi-release root</a>. This
prevents the jar from containing a file at
<code>META-INF/versions/9/OSGI-INF/MANIFEST.MF</code>, which was causing
<a
href="https://redirect.github.com/jspecify/jspecify/issues/484#issuecomment-2819506604">trouble
for some users</a>, particularly on Android.</li>
<li>The JSpecify <code>module-info.class</code> now contains its version
number.</li>
<li>We have made various improvements to our Javadoc. While the latest
docs are always available at <a
href="https://jspecify.dev/docs/api/">jspecify.dev/docs/api</a>, this
release makes our improvements visible in the source files in your
IDE.</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/jspecify/jspecify/commit/ce9bec0b8895f424d999d31e3a1bd33694ee4c0c"><code>ce9bec0</code></a>
Set version to 1.0.1.</li>
<li><a
href="https://github.com/jspecify/jspecify/commit/7c7f0cf049a4d3b2fb9e97213ed76ea4ae16e6d5"><code>7c7f0cf</code></a>
Migrate to com.vanniktech.maven.publish.</li>
<li><a
href="https://github.com/jspecify/jspecify/commit/2789f6715b05307716a8534c1c2cd5d6e55e9ad4"><code>2789f67</code></a>
Bump yaml from 1.10.2 to 1.10.3 in /docs (<a
href="https://redirect.github.com/jspecify/jspecify/issues/853">#853</a>)</li>
<li><a
href="https://github.com/jspecify/jspecify/commit/1638ca0b9b8249ebdd0100daa976d0c553432d4b"><code>1638ca0</code></a>
Bump svgo from 3.3.2 to 3.3.4 in /docs (<a
href="https://redirect.github.com/jspecify/jspecify/issues/852">#852</a>)</li>
<li><a
href="https://github.com/jspecify/jspecify/commit/4e80178f7e3ef556169c7866e2c91dae3f69750d"><code>4e80178</code></a>
Place <code>module-info</code> in the root of the jar. (<a
href="https://redirect.github.com/jspecify/jspecify/issues/809">#809</a>)</li>
<li><a
href="https://github.com/jspecify/jspecify/commit/5b679e09a4f42956cdb4d88bc3db8129fdd6bd9f"><code>5b679e0</code></a>
Codex found a few more questions the FAQ already answers. (<a
href="https://redirect.github.com/jspecify/jspecify/issues/848">#848</a>)</li>
<li><a
href="https://github.com/jspecify/jspecify/commit/20198997c948e1e3cd9a8f36f6d812e549fcbbda"><code>2019899</code></a>
Link to the new location of the design FAQ and to specific sections. (<a
href="https://redirect.github.com/jspecify/jspecify/issues/845">#845</a>)</li>
<li><a
href="https://github.com/jspecify/jspecify/commit/f01eac9dbb76fffe1dbd191148796b2200f074d0"><code>f01eac9</code></a>
batch of javadoc revisions for clarity and completeness (<a
href="https://redirect.github.com/jspecify/jspecify/issues/671">#671</a>)</li>
<li><a
href="https://github.com/jspecify/jspecify/commit/c4eff3117b23ed45614bd15c83a3415aea225f2b"><code>c4eff31</code></a>
Import the nullness design FAQ as Markdown. (<a
href="https://redirect.github.com/jspecify/jspecify/issues/838">#838</a>)</li>
<li><a
href="https://github.com/jspecify/jspecify/commit/75fb9cf403fdeaf590131e36922a71799a308157"><code>75fb9cf</code></a>
Bump websocket-driver from 0.7.4 to 0.7.5 in /docs (<a
href="https://redirect.github.com/jspecify/jspecify/issues/835">#835</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/jspecify/jspecify/compare/v1.0.0...v1.0.1">compare
view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
</details>
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>1 parent 59cd0fa commit 4a570b2
1 file changed
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
15 | 15 | | |
16 | 16 | | |
17 | 17 | | |
18 | | - | |
| 18 | + | |
19 | 19 | | |
20 | 20 | | |
21 | 21 | | |
| |||
0 commit comments