Skip to content

What changed (17 files) - #317

Merged
thanos merged 1 commit into
mainfrom
v1.3.1/release_prep
Oct 9, 2026
Merged

thanos merged 1 commit into
mainfrom
v1.3.1/release_prep

Conversation

@thanos

@thanos thanos commented Oct 9, 2026

Copy link
Copy Markdown
Collaborator
  • Version: mix.exs is now 1.3.1, and the new docs/release_notes_v1_3_1.md is registered in the docs under the release notes group.
  • CHANGELOG:
    • The [Unreleased] fixes are now ## [1.3.1] - 2026-10-09, with a short summary and an empty [Unreleased] section above.
    • I added entries for your post-merge commit e2abf91: the steadier streaming memory test and the livebook pin updates.
    • The comparison links are updated: [Unreleased] compares from v1.3.1, and [1.3.1] compares v1.3.0 to v1.3.1.
  • Release notes: written for users, covering the Nx speedups, the shuffle fix, the livebooks and the doc corrections. It says no code changes are needed to upgrade.
  • ROADMAP and README: both have a v1.3.1 entry.
  • Version references: "1.3.0" became "1.3.1" in the installation guide's version check and the troubleshooting bug-report template. The livebook status page now says every shipped notebook runs in CI, and I fixed a typo there ("directry").
  • Install pins: the remaining ~> 1.2 pins are now ~> 1.3. That covers one shipped livebook (06_05), three notebooks, three livebook scripts, and the storage-providers and migrating-from-Python guides. The 1.1 migration guide keeps ~> 1.1, since it documents that upgrade.
  • I left the code comments and test names that say "1.3.0" alone. They describe the shuffle order that 1.3.0 produced, which is still accurate.

Verified

  • Format, compile, credo and docs pass, and the test suite passes (1,679 tests, 0 failures).
  • mix hex.build produces a version 1.3.1 package. I built it in the scratchpad and deleted it.
  • I simulated the release workflow's checks:
    • The tag v1.3.1 will match mix.exs, and ## [1.3.1] exists in the CHANGELOG.
    • The GitHub release body will come from docs/release_notes_v1_3_1.md.
    • The CHANGELOG fallback also extracts the 1.3.1 section correctly.
  • All 17 shipped livebooks pass against this code, and 06_05 passes from Hex with its new pin.

To release: commit this branch, merge it to main, then push the tag v1.3.1. The release workflow verifies the build, creates the GitHub release and publishes to Hex, as it did for 1.3.0.

- Version: mix.exs is now 1.3.1, and the new docs/release_notes_v1_3_1.md is registered in the docs under the release notes group.
- CHANGELOG:
  - The [Unreleased] fixes are now ## [1.3.1] - 2026-10-09, with a short summary and an empty [Unreleased] section above.
  - I added entries for your post-merge commit e2abf91: the steadier streaming memory test and the livebook pin updates.
  - The comparison links are updated: [Unreleased] compares from v1.3.1, and [1.3.1] compares v1.3.0 to v1.3.1.
- Release notes: written for users, covering the Nx speedups, the shuffle fix, the livebooks and the doc corrections. It says no code changes are needed to upgrade.
- ROADMAP and README: both have a v1.3.1 entry.
- Version references: "1.3.0" became "1.3.1" in the installation guide's version check and the troubleshooting bug-report template. The livebook status page now says every shipped notebook runs in CI, and I fixed a typo there ("directry").
- Install pins: the remaining ~> 1.2 pins are now ~> 1.3. That covers one shipped livebook (06_05), three notebooks, three livebook scripts, and the storage-providers and migrating-from-Python guides. The 1.1 migration guide keeps ~> 1.1, since it documents that upgrade.
- I left the code comments and test names that say "1.3.0" alone. They describe the shuffle order that 1.3.0 produced, which is still accurate.

Verified
- Format, compile, credo and docs pass, and the test suite passes (1,679 tests, 0 failures).
- mix hex.build produces a version 1.3.1 package. I built it in the scratchpad and deleted it.
- I simulated the release workflow's checks:
  - The tag v1.3.1 will match mix.exs, and ## [1.3.1] exists in the CHANGELOG.
  - The GitHub release body will come from docs/release_notes_v1_3_1.md.
  - The CHANGELOG fallback also extracts the 1.3.1 section correctly.
- All 17 shipped livebooks pass against this code, and 06_05 passes from Hex with its new pin.

To release: commit this branch, merge it to main, then push the tag v1.3.1. The release workflow verifies the build, creates the GitHub release and publishes to Hex, as it did for 1.3.0.
@thanos
thanos merged commit abc6a87 into main Oct 9, 2026
12 checks passed
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