chore: release main - #3
Open
hyuki0130 wants to merge 1 commit into
Open
Conversation
hyuki0130
force-pushed
the
release-please--branches--main
branch
27 times, most recently
from
August 5, 2026 10:51
48c1928 to
3b899c9
Compare
hyuki0130
force-pushed
the
release-please--branches--main
branch
2 times, most recently
from
August 5, 2026 12:50
60c8937 to
324a19f
Compare
hyuki0130
force-pushed
the
release-please--branches--main
branch
8 times, most recently
from
August 14, 2026 08:06
ced1098 to
c0f69ac
Compare
hyuki0130
force-pushed
the
release-please--branches--main
branch
11 times, most recently
from
August 22, 2026 16:02
0c0ec5c to
7d2e100
Compare
hyuki0130
pushed a commit
that referenced
this pull request
Aug 22, 2026
…e numbers Staging is done, so the section that said "NOT run from here" is now the record of what was actually run. Open question #3 — which of R2's two public surfaces staging had on — is answered: no r2.dev URL, one custom domain, disabled rather than removed so rollback stays a one-field PUT instead of a DNS change. The before/after is a real object, not a 404 probe. A missing key answers 404 whether the bucket is open or shut, so the first probe proved nothing; the measurement that counts is 200 with 12856 bytes becoming 401. Also written down, because both nearly undid the flip and neither is obvious from the code: - R2_PUBLIC_URL has to be RELATIVE. The absolute form reaches the gate and looks right while re-creating exactly the rows the cleanup deleted. The warning was already in this file and got read too late. - Editing Cloud Run alone does not survive a deploy: deploy.yml uses --set-env-vars and sources the value from a GitHub secret, so the next deploy silently reverts it. And the secret is the _NEW-suffixed one — the unsuffixed name belongs to the old project. The order staging used (truncate, flip, then fix the URL) was wrong and survived only because the database was empty. That is stated plainly so production does not inherit it. The #83 / #81 references throughout were never real — the repo has only #4 and #5. They are replaced with the checklist items that actually block.
hyuki0130
force-pushed
the
release-please--branches--main
branch
9 times, most recently
from
August 24, 2026 18:14
77394f6 to
ca6ca74
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
openstoa-sdk: 0.1.3
0.1.3 (2026-09-05)
Features
Bug Fixes
Refactoring
openstoa-channel: 0.1.3
0.1.3 (2026-09-05)
Dependencies
openstoa-cli: 0.1.3
0.1.3 (2026-09-05)
Features
Dependencies
openstoa-commands: 0.1.3
0.1.3 (2026-09-05)
Features
Dependencies
openstoa-mcp: 0.1.3
0.1.3 (2026-09-05)
Features
Dependencies
openstoa-server: 0.1.2
0.1.2 (2026-09-05)
Features
Bug Fixes
Performance
Refactoring
This PR was generated with Release Please. See documentation.