chore(main): release w3console 1.10.0 #112
Merged
Conversation
This file contains 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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
github-actions
bot
force-pushed
the
release-please--branches--main--components--w3console
branch
4 times, most recently
from
13e8852
to
44b6f30
Compare
github-actions
bot
force-pushed
the
release-please--branches--main--components--w3console
branch
from
44b6f30
to
7864595
Compare
This was mainly a sweep of uses of `h-screen`, as it was breaking on viewports shorter than the page contents, which was particularly nasty on the Pricing page, which is long. I've also: * Tweaked how the rooster shows up on small-width screens * Made the "Terms of Service" text on the login screen black rather than white for readability * Made the hamburger menu icon red rather than write for readability * Changed "w3up" to "Storacha" Unfortunately, we don't have Storybook and Chromatic (or similar) to see all the diffs, but I've screenshotted what I could. Note that these are all full-page screenshots; the fact that the befores are cut off at the top is exactly the problem I was solving here. 🙂 Plenty of this is subjective; thoughts, feedback, and corrections are more than welcome. ### Before      ### After     
github-actions
bot
changed the title
github-actions
bot
force-pushed
the
release-please--branches--main--components--w3console
branch
from
7864595
to
e42fd67
Compare
github-actions
bot
force-pushed
the
release-please--branches--main--components--w3console
branch
from
e42fd67
to
c0645ab
Compare
github-actions
bot
force-pushed
the
release-please--branches--main--components--w3console
branch
from
c0645ab
to
e00fdb2
Compare
# Issue If the `NEXT_PUBLIC_W3UP_PROVIDER` environment variable is not set, the app will use `did:web:web3.storage` as the default storage provider. That works well if we are pointing to Prod environment (https://up.web3.storage), however, if we use the Staging environment (https://staging.up.web3.storage) it will fail to provision the space because the default provider is invalid for Staging. # Fix - Verify if the Space Provisioning result contains an error. If so, throw the error to prevent the user from continuing the flow and attempting to upload files. - Updated Docs and sample Env Vars. --------- Co-authored-by: Alan Shaw <alan.shaw@protocol.ai>
So we're all on the same version (and package manager).
Just a tiny copy change.
I've updated the workflow to use the `old-main` branch to deploy the `https://console.web3.network` app.
I've fixed the `deploy-storacha.yml` workflow to build previews and changelogs, run tests, and create releases using the same conditionals we had while deploying to `https://console.web3.storage`.
github-actions
bot
force-pushed
the
release-please--branches--main--components--w3console
branch
from
e00fdb2
to
d871970
Compare
# Goals use up.storacha.network for service URL # Implementation update deploy scripts in github.
github-actions
bot
force-pushed
the
release-please--branches--main--components--w3console
branch
from
d871970
to
d7f998b
Compare
hannahhoward
deleted the
release-please--branches--main--components--w3console
branch
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.
🤖 I have created a release beep boop
1.10.0 (2024-09-04)
Features
Bug Fixes
Other Changes
packageManager(#117) (5f135df)This PR was generated with Release Please. See documentation.