revert to recipe state of v6.8.0 #55

Merged
val merged 1 commits from revert-changes into main 2026-01-15 15:48:56 +00:00
Owner

I reverted all the changes that happend after the last known running deployment v6.8.0.
I suggest to move on to v6.8.2 and so increase all the env-version-numbers as well to prevent further chaos (already did this in the current pull request)

From there on I suggest to first update matrix-synapse version and then start hacking again on upload-limit and auto-join rooms.

Question on release-progress. Would I now accept the pull request and afterwards run abra recipe sync and abra recipe release or do I do this on this branch and afterwerds accepting the pull request?

I reverted all the changes that happend after the last known running deployment `v6.8.0`. I suggest to move on to `v6.8.2` and so increase all the env-version-numbers as well to prevent further chaos (already did this in the current pull request) From there on I suggest to first update matrix-synapse version and then start hacking again on upload-limit and auto-join rooms. Question on release-progress. Would I now accept the pull request and afterwards run `abra recipe sync` and `abra recipe release` or do I do this on this branch and afterwerds accepting the pull request?
val added 1 commit 2026-01-15 10:17:47 +00:00
Author
Owner

Further notice: I deployed it as --chaos on a running instance and it worked.

Further notice: I deployed it as `--chaos` on a running instance and it worked.
decentral1se requested review from moritz 2026-01-15 10:24:06 +00:00
decentral1se requested review from notplants 2026-01-15 10:24:06 +00:00
decentral1se requested review from cas 2026-01-15 10:24:27 +00:00
decentral1se requested review from simon 2026-01-15 10:24:27 +00:00
Owner

@val someone else might need to chime in. for the recipes I have worked on I have still had some issues with the abra recipe sync and abra recipe release commands

so far instead I have been using git commands directly to do a new release:

git tag -a "6.8.2+v1.139.2" -m "publish 6.8.2+v1.139.2"
git push --tags
@val someone else might need to chime in. for the recipes I have worked on I have still had some issues with the `abra recipe sync` and `abra recipe release` commands so far instead I have been using git commands directly to do a new release: ``` git tag -a "6.8.2+v1.139.2" -m "publish 6.8.2+v1.139.2" git push --tags ```
Author
Owner

ok thanks. I chatted with @simon directly and figured out I preferibly do the merge first and try my best releasing in an extra step directly on main (which makes sense as tags are not branch-specific).
So I'll give it a shot now :)

ok thanks. I chatted with @simon directly and figured out I preferibly do the merge first and try my best releasing in an extra step directly on main (which makes sense as tags are not branch-specific). So I'll give it a shot now :)
val merged commit 0e55594727 into main 2026-01-15 15:48:56 +00:00
val deleted branch revert-changes 2026-01-15 15:48:56 +00:00
Sign in to join this conversation.
No description provided.