chore: version packages - #2163
Merged
Merged
Conversation
github-actions
Bot
requested review from
LeonardoVieira1630,
PedroBinotto,
alextnetto,
brunod-e and
pikonha
as code owners
September 14, 2026 13:26
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
github-actions
Bot
force-pushed
the
changeset-release/dev
branch
3 times, most recently
from
September 15, 2026 14:03
9a6a7fd to
34f5ea9
Compare
github-actions
Bot
force-pushed
the
changeset-release/dev
branch
from
September 15, 2026 17:01
34f5ea9 to
6135cfa
Compare
github-actions
Bot
force-pushed
the
changeset-release/dev
branch
from
September 15, 2026 17:41
6135cfa to
c92fb05
Compare
github-actions
Bot
force-pushed
the
changeset-release/dev
branch
from
September 15, 2026 19:05
c92fb05 to
deb7eed
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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to dev, this PR will be updated.
Releases
@anticapture/dashboard@2.16.0
Minor Changes
#2146
c7aed8cThanks @brunod-e! - Add a recursive calldata decoder to proposal actions and a standalone /tools/decoder page.#2155
55af56bThanks @brunod-e! - Queue and execute proposals through the relayer for free when it is funded, with the wallet flow as fallback.Patch Changes
3935d42Thanks @brunod-e! - Stop retrying failed HTTP requests in React Query (retry network errors once): each retry against a failingroute counted toward the gateway circuit breaker, so one page view could take a DAO offline.
@anticapture/relayer@1.3.0
Minor Changes
33d6572Thanks @LeonardoVieira1630! - Add POST /internal/webhook, a receiver for notification-system events. Theroute lives under /internal/ so gateful's /:dao/relay/* proxy cannot reach
it — only Railway's private network can. When the body carries
metadata.proposalIdfor this relayer's own DAO, the relayer reads theproposal's on-chain state and sponsors queue() (Succeeded) or execute()
(Queued, eta passed) through the existing enactment service; events for
other DAOs (
metadata.daoId) are ignored. The route is not part of thepublic OpenAPI spec. The server now binds to
::so Railway privatenetworking can reach it.
@anticapture/api@1.8.3
Patch Changes
#2148
82179d9Thanks @brunod-e! - Serve proposals without waiting on RPC: the latest block is refreshed stale-while-revalidate, bounded to 60s of staleness.Requests fall back to the indexed proposal status when the RPC is down instead of failing.
#2149
f144c5cThanks @brunod-e! - Revenue, token price and treasury serve the last known or empty data instead of 5xx when Dune or CoinGecko isunhealthy, token properties keep the last known price, all counted on degraded_upstream_responses_total; fix the FLUID CoinGecko id.
@anticapture/gateful@1.8.2
Patch Changes
#2148
82179d9Thanks @brunod-e! - Circuit breakers open per DAO route on a windowed failure rate, tunable via theCIRCUIT_BREAKER_*variables in apps/gateful/src/config.ts, with route keys derived from the path and separate keys for fan-out and health probes, whose circuits are no longer reported in the DAO health summary.The Redis cache serves stale entries when the upstream fails, and each lookup is counted once.
#2162
888097fThanks @brunod-e! - Forward the relayer's own error responses (e.g.503 RELAYER_LOW_BALANCE,{ code, message }) to clients instead ofreplacing them with a generic 500, and stop counting them as circuit-breaker failures: the relayer answered, it is not down.