Skip to content

fix: add staging plans to plan definition list - #640

Merged
travis merged 3 commits into
mainfrom
fix/staging-plans
Jan 23, 2026
Merged

fix: add staging plans to plan definition list#640
travis merged 3 commits into
mainfrom
fix/staging-plans

Conversation

@travis

@travis travis commented Jan 23, 2026

Copy link
Copy Markdown
Contributor

otherwise we see errors on the plan page in staging

otherwise we see errors on the plan page in staging
@travis
travis temporarily deployed to preview-640/merge January 23, 2026 17:28 — with GitHub Actions Inactive
@travis
travis temporarily deployed to preview-640/merge January 23, 2026 17:30 — with GitHub Actions Inactive
@github-actions

github-actions Bot commented Jan 23, 2026

Copy link
Copy Markdown
Contributor

@travis
travis requested a review from a team January 23, 2026 17:41

@volmedo volmedo left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Comment on lines +203 to +204
console.log("PLAN", plan)
console.log("IS PLAN LOADING", isPlanLoading)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe you want to remove these before merging?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

a good catch thx!

@volmedo

volmedo commented Jan 23, 2026

Copy link
Copy Markdown
Contributor

also, does the logic showing these need to be adjusted to filter plans depending on the environment? It wouldn't be great to show staging plans in prod.

@travis

travis commented Jan 23, 2026

Copy link
Copy Markdown
Contributor Author

also, does the logic showing these need to be adjusted to filter plans depending on the environment? It wouldn't be great to show staging plans in prod.

ah, this isn't used to select plans, just to find a human readable name for them - if people have staging plans in production they'll see this but that's a good thing - that would be a very weird state of affairs we'd need to fix manually

@travis
travis deployed to preview-640/merge January 23, 2026 18:01 — with GitHub Actions Active
@travis
travis merged commit 7774e51 into main Jan 23, 2026
5 checks passed
travis pushed a commit that referenced this pull request Jan 26, 2026
🤖 I have created a release *beep* *boop*
---


##
[2.20.0](console-v2.19.2...console-v2.20.0)
(2026-01-23)


### Features

* add egress reporting to account/usage/get
([#611](#611))
([df39e6f](df39e6f))


### Fixes

* add staging plans to plan definition list
([#640](#640))
([7774e51](7774e51))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants