Set an explicit default Gitpod host for existing users

[filiptronicek]

Description

Preps for NEXT-3410 by making sure all users who use the extension get their host set to https://gitpod.io, if they haven't set it to something else manually.

Related Issue(s)

Fixes NEXT-3408

How to test

1. Make a fresh install of the extension
2. In Chrome, go into Application -> Extension storage -> Gitpod -> Sync and see the value is set to "https://gitpod.io". If not, go to a page the extension is active on (such as this PR) and see again.

The rollout plan here is to let the extension explicitly set the hostname for a couple of weeks and then roll out a new version where the default is app.gitpod.io.

[Copilot]

Pull Request Overview

This PR sets an explicit default Gitpod host for users who have not configured their endpoint manually. It updates the storage logic in both the dashboard content script and the button component to ensure the default endpoint ("https://gitpod.io") is applied appropriately.

• Simplifies the conditional check for updating the endpoint in the dashboard script.
• Removes the default parameter from the useStorage hook in the button component and adds an effect to initialize the default if unset.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
src/contents/gitpod-dashboard.ts	Updates the logic for conditionally updating the stored endpoint.
src/button/button.tsx	Removes the default from useStorage and adds a useEffect to set the default endpoint.

Comments suppressed due to low confidence (2)

src/button/button.tsx:53

• [nitpick] Default address initialization logic appears in multiple locations; consider consolidating this logic into a shared module to prevent potential inconsistencies.

const actions = useMemo(() => {

src/contents/gitpod-dashboard.ts:26

• Verify that removing the explicit check against DEFAULT_GITPOD_ENDPOINT does not unintentionally override a user-set default when running on gitpod.io. Consider ensuring that the logic maintains the intended behavior in all hosting environments.

if (!currentlyStoredEndpoint || new URL(currentlyStoredEndpoint).host !== currentHost) {

[kylos101]

@filiptronicek should we bump the version in package.json?

[kylos101]

Works as advertised. 😄

✅ to unblock

I'm not sure how we generally ship, but it seems like we should bump the version before we do (ref: #192 (review))

[filiptronicek]

I usually make version upgrades with yarn version --patch and push to main, because it also takes care of creating the tag. See the relevant section in the README:

browser-extension/README.md

Lines 69 to 70 in a7b3145

	1. Bump up the version value inside `package.json` (`yarn version --patch` or `yarn version --minor`)
	1. Push your changes to `main`