Library

All

Describe the feature that you would like added

At the moment v-build and anyone triggering v9 release is noticed only when it's already too late - broken release 🥲.

We need to improve current situation in 2 areas.

✅ 1. Adding integration tests to make sure following things works:

• we always publish to npm expected assets
  • to mitigate regressions like fix: update .npmignore files to resolve npm8/node16 regression with npm publish for v9 packages #27741, fix: dont ignore lib, lib-commonjs and lib-amd files #27736, fix (v8): update more .npmignore files to resolve node16 regression with npm publishing #27745
• custom logic used within release pipelines works
  • to mitigate issues like fix(scripts-update-release-notes): properly handle git for-each-ref cmd call to not fail release notes update #27757

✅ 2. Switch to files instead of npmignore

• to mitigate regressions like fix: update .npmignore files to resolve npm8/node16 regression with npm publish for v9 packages #27741,
• for rock solid control over what is being shipped ( npmignore and github ignore doesn't work well together )

3. Fallbacks when things out of our control fail:

Npm registry failures:

We need to implement proper fallback behaviours for cases where npm registry errors during npm publish.

This situation puts repo into invalid state, which blocks every contributor. Only remedy ATM is to manually trigger beachball , create PR and merge, which is far from ideal.

We need to implement some graceful fallback mechanism for these situations which is fully automatic.

Have you discussed this feature with our team

v-build

Additional context

No response

Validations

• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.