Skip to content

Update @datocms/astro 0.6.12 → 0.6.13 (minor) - #454

Merged
milailijevic merged 2 commits into
mainfrom
depfu/update/npm/@datocms/astro-0.6.13
Jul 23, 2026
Merged

Update @datocms/astro 0.6.12 → 0.6.13 (minor)#454
milailijevic merged 2 commits into
mainfrom
depfu/update/npm/@datocms/astro-0.6.13

Conversation

@depfu

@depfu depfu Bot commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ @​datocms/astro (0.6.12 → 0.6.13) · Repo

Release Notes

0.6.13

Automatic sizes="auto" for lazy-loaded responsive images

When you don't pass an explicit sizes prop (and the image isn't priority), the image components now emit sizes="auto, 100vw" together with loading="lazy".

On supporting browsers (Chrome/Edge 126+, Opera, Samsung Internet, Firefox 150+) the browser picks the optimal srcset candidate from the image's real laid-out width instead of assuming the full viewport width (100vw) — often a much smaller download. Browsers without support (e.g. Safari) fall back to 100vw, i.e. the previous behavior, so there is no regression.

  • An explicit sizes (prop, or coming from the responsiveImage GraphQL query) still takes precedence — we never override it.
  • priority images are unchanged (they load eagerly, and sizes="auto" requires loading="lazy").
  • Applies to both the SSR/native components and the JavaScript lazy-loading components.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 4 commits:


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu Bot added the depfu label Jun 25, 2026
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jun 25, 2026

Copy link
Copy Markdown

Deploying head-start with  Cloudflare Pages  Cloudflare Pages

Latest commit: 80f258f
Status: ✅  Deploy successful!
Preview URL: https://6b4c5683.head-start.pages.dev
Branch Preview URL: https://depfu-update-npm--datocms-as.head-start.pages.dev

View logs

@depfu
depfu Bot force-pushed the depfu/update/npm/@datocms/astro-0.6.13 branch from ccd1239 to 80f258f Compare July 17, 2026 11:05
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jul 17, 2026

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
head-start 4b7654e Commit Preview URL

Branch Preview URL
Jul 23 2026, 01:06 PM

@milailijevic
milailijevic merged commit e8a5029 into main Jul 23, 2026
5 checks passed
@milailijevic
milailijevic deleted the depfu/update/npm/@datocms/astro-0.6.13 branch July 23, 2026 13:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants