build: properly handle whether builds should be stamped for release (#42319)
Properly build snapshot or release stamped versions of the builds based on the provided context from the ng-dev toolset. PR Close #42319
This commit is contained in:
parent
4afad03312
commit
f1d12bf749
|
@ -22,11 +22,11 @@ export const release: ReleaseConfig = {
|
|||
'@angular/service-worker',
|
||||
'@angular/upgrade',
|
||||
],
|
||||
buildPackages: async () => {
|
||||
buildPackages: async (stampForRelease: boolean) => {
|
||||
// The buildTargetPackages function is loaded at runtime as the loading the script causes an
|
||||
// invocation of bazel.
|
||||
const {buildTargetPackages} = require(join(__dirname, '../scripts/build/package-builder'));
|
||||
return buildTargetPackages('dist/release-output', false, 'Release', true);
|
||||
return buildTargetPackages('dist/release-output', false, 'Release', stampForRelease);
|
||||
},
|
||||
releaseNotes: {
|
||||
hiddenScopes: ['aio', 'dev-infra', 'docs-infra', 'zone.js'],
|
||||
|
|
Loading…
Reference in New Issue