Skip to content

Bug: Incorrectly resolved SPFx project upgrade rules #2610

@waldekmastykarz

Description

@waldekmastykarz

Let me just share what is different between the two sets of instructions.

From 1.12.0 to 1.13 beta:

./config/copy-assets.json
-------------------------
Update copy-assets.json deployCdnPath:
{
  "deployCdnPath": "./release/assets/"
}

./config/deploy-azure-storage.json
----------------------------------
Update deploy-azure-storage.json workingDir:
{
  "workingDir": "./release/assets/"
}

./.gitignore
------------
To .gitignore add the 'release' folder:
release

From 1.12.1 to 1.13 beta:

./config/copy-assets.json
-------------------------
Update copy-assets.json deployCdnPath:
{
  "deployCdnPath": "temp/deploy"
}

./.gitignore
------------
From .gitignore remove the 'release' folder:
release

So at the end of the day, if I compare my project upgraded from 1.12.0 and my project upgraded from 1.12.1, the files copy-assets.json and .gitignore are different.

Originally posted by @PathToSharePoint in #2607 (comment)

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions