Skip to content

v4.6.0

Choose a tag to compare

View all tags
@n8behavior n8behavior released this 26 Oct 00:23
· 34 commits to main since this release
v4.6.0
6501ddb
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Level: minor, 4.6.0.

Waves in this release: Wave 44: a smoother wave.

Wave 44: a smoother wave:

  • #1514: After a rollback of riff-server to the release before, a line of riff in riff chat still posts (#1515).
  • #1509: An unknown result of riff release check tells the other leads that the checks could not all run (#1513).
  • #1480: riff who --long shows the image of each wave and of each session container (#1510).
  • #1467: A wave on more hosts sends each message about a pull request one time (#1507).
  • #1497: A line that riff writes in riff chat is no approval of the owner: riff release approve skips it (#1506).
  • #1479: A merge queue on main: the wave leaves a queued pull request alone (#1505).
  • #1494: riff release cut asks the owner for nothing; the only ask is the line that the deploy waits (#1504).
  • #1445: The commits that riff makes for itself carry no signature (#1502).
  • #1482: The daemon reads [release] from the merged riff.toml, not from the working tree of the main clone (#1501).
  • #1478: The book says the release gate of riff wave end in one place (#1500).
  • #1483: The diagram of Run the wave sends an UNKNOWN that turns MERGEABLE to the verify (#1499).
  • #1491: The book says that riff starts the lead again on the new riff after a daemon starts again (#1498).

What's Changed

Changes

  • The diagram of Run the wave sends an UNKNOWN that turns MERGEABLE to the verify by @n8behavior in #1499
  • The book says the release gate of riff wave end in one place by @n8behavior in #1500
  • The book says that riff starts the lead again on the new riff after a daemon starts again by @n8behavior in #1498
  • The daemon reads [release] from the merged riff.toml, not from the working tree of the main clone by @n8behavior in #1501
  • The commits that riff makes for itself carry no signature by @n8behavior in #1502
  • A wave on more hosts sends each message about a pull request one time by @n8behavior in #1507
  • A merge queue on main: the wave leaves a queued pull request alone by @n8behavior in #1505
  • riff release cut asks the owner for nothing; the only ask is the line that the deploy waits by @n8behavior in #1504
  • An unknown result of riff release check tells the other leads that the checks could not all run by @n8behavior in #1513
  • A line that riff writes in riff chat is no approval of the owner: riff release approve skips it by @n8behavior in #1506
  • riff who --long shows the image of each wave and of each session container by @n8behavior in #1510
  • After a rollback of riff-server to the release before, a line of riff in riff chat still posts by @n8behavior in #1515

Full Changelog: v4.5.0...v4.6.0

Images

  • ghcr.io/como-technologies/riff-base@sha256:2799cd2e7c6e23ab4b9b576ad1331e7315044378a490317624c93d3d984ad5b1
  • ghcr.io/como-technologies/riff-rust@sha256:eb0c0920825ef44e72e4183bb8a4a93a5add5a09422a4f3e73ec61cde19ccfe1

Contributors

n8behavior
Assets 5
Loading