Skip to content

Conversation

@danielroe
Copy link
Member

πŸ”— Linked issue

backport of #3792

❓ Type of change

  • πŸ“– Documentation (updates to the documentation, readme, or JSdoc annotations)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • 🧹 Chore (updates to the build process or auxiliary tools and libraries)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

this backports #3792

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

@danielroe danielroe requested a review from pi0 as a code owner November 18, 2025 12:04
@vercel
Copy link

vercel bot commented Nov 18, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
nitro.build Ready Ready Preview Comment Nov 18, 2025 0:05am

@danielroe danielroe changed the title feat: add manifest.deploymentId (#3792) feat: add manifest.deploymentId Nov 18, 2025
@pi0
Copy link
Member

pi0 commented Nov 18, 2025

What would be benefit of this backport without agnostic skew detection support in v2?

I think would probably be more valuable if we add this flag to std-env (tracker: unjs/std-env#59)

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