Repository navigation
chore: update OpenAPI to f816e2612cac - #333
ant-release-bot wants to merge 1 commit into
Conversation
commit: |
|
| mean | stddev | min | max | |
|---|---|---|---|---|
| PR | 276.7 ms | 6.2 ms | 268.8 ms | 293.1 ms |
| base | 276.5 ms | 5.2 ms | 269.6 ms | 291.9 ms |
Δ (PR vs base): — +0.2 ms (+0.1%)
Measured with hyperfine on ubuntu-latest (3 warmup runs, 20 timed runs). CI numbers carry ±a few ms of runner jitter; treat small deltas as noise.
![ask-bonk[bot]](https://avatars.githubusercontent.com/in/2454580?s=60&v=4){kind=small}
| const bundle = process.env.FORGE_OPENAPI_BUNDLE; | ||
| // Bump this SHA to generate the commands from a new release. | ||
| const FORGE_OPENAPI_VERSION = "ec19e9f82e219137a547ca40f48babe71c69e481"; | ||
| const FORGE_OPENAPI_VERSION = "f816e2612cac2b5489403d1011e8ff0d362d8cf0"; |
There was a problem hiding this comment.
This is a downgrade, not an update: the Forge release for f816e261 was published at 2026-10-15T16:06:03Z, whereas the ec19e9f revision currently pinned on main was published at 2026-10-15T21:06:08Z. Regenerating from the older revision removes the existing CASB, DLP validator, and Priority Intelligence command surface. Keep the newer pin (or move forward to a later release) so this automated update does not ship a backwards-incompatible deletion.
| const FORGE_OPENAPI_VERSION = "f816e2612cac2b5489403d1011e8ff0d362d8cf0"; | |
| const FORGE_OPENAPI_VERSION = "ec19e9f82e219137a547ca40f48babe71c69e481"; |
|
🤖 I've done a thorough review of your PR. Updates the OpenAPI revision and regenerates the command surface.
|
|
Closing as this is trying to update to the wrong version - see #334 |
2 participants
Updates cf to
openapi@f816e2612cac2b5489403d1011e8ff0d362d8cf0.f816e2612cac2b5489403d1011e8ff0d362d8cf0This PR is maintained automatically by the Update OpenAPI workflow.