build(deps): bump next from 10.0.0 to 10.0.1#142
Merged
Conversation
Bumps [next](https://github.com/vercel/next.js) from 10.0.0 to 10.0.1. - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v10.0.0...v10.0.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
dependabot-preview
Bot
added
the
dependencies
tsahimatsliah
added a commit
that referenced
this pull request
May 19, 2026
…pics grid, editorial endcap
Round 3 of UX revisions:
- New BriefFloatingTabs: a floating pill at bottom-center while the
user reads the brief ("Your brief" active, "For you" secondary).
Clicking "For you" smooth-scrolls to the feed sentinel; scrolling
past it morphs the pill into a full-width top-anchored bar with
[← Back to brief | separator | ExploreChipsBar]. Chips are sourced
from the same useFeedTagsList hook as the existing strip.
- MainFeedLayout: when briefing_home is enabled on the logged-in
homepage, the original ExploreChipsBar is suppressed so it does
not duplicate the docked one above the feed.
- CoverHeader: dropped the redundant segmented tabs and the 3-dot
collapse/dismiss menu (the floating dock replaces them). The header
is now a single block: edition meta + greeting + 1-line deck. Top
gap reduced.
- CoverGrid: "Worth your attention" is no longer a 3-col card grid;
it is now a scannable numbered list (01, 02, 03 …) with source +
read time meta on the top row, big title underneath, community
quote below, and engagement counters right-aligned. Each row is
one big clickable surface.
- CoverTopics: killed the oval chip selector. All four topic digests
now render at once in a 2x2 card grid, each with a colored topic
bar, read time, headline, and 3-line TL;DR — user gets the gist of
every topic without clicking.
- CoverClosing: rebuilt from scratch as an editorial endcap. Centered
layout, horizontal rule with "END OF BRIEF" tag, large sign-off
headline + sub, progress bar only if still in progress, single
strong CTA pointing to the feed, and a colophon line ("Edition #142
· Tue, May 19 · Filed by daily.dev") at the bottom.
Co-authored-by: Cursor <cursoragent@cursor.com>
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
1 participant
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.
Bumps next from 10.0.0 to 10.0.1.
Release notes
Sourced from next's releases.
Commits
3c33794v10.0.1d4a92d9Update example for Image Component (#18762)89a3249v10.0.1-canary.7f791577Ensure redirect from GS(S)P doesn't render (#18749)b87b2d4add rewrites in storybook preset (#18364)44ea598Update next-translate example to support Next 10 with i18n routing (#18480)4620dccUpdate Gatsby migration guide to include next/image. (#18741)27d7b76Prevent Next.js from removing all of its styles on hydration (#18723)b1503e1Fix dynamic css unloading (#17173)56bd464v10.0.1-canary.6Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language@dependabot badge mewill comment on this PR with code to add a "Dependabot enabled" badge to your readmeAdditionally, you can set the following in your Dependabot dashboard: