Remove package.json from stable in advance of release. For context, for some reason stable did not have package.json. When we release to npm, package.json gets copied from master into the package. Removing for now so we don't accidentally end up with conflicting package.json when we release since stable has a different structure than the npm package (I had just recently added package.json to stable after an error pulling in that branch to Design System site).
For future, we should revisit the stable branch structure and likely mirror what is in the npm package.
What testing has been done on this PR?
Any background context you want to provide?
What are the relevant issues?
Screenshots (if appropriate)
Is this change backward compatible or could it be a breaking change for the official HPE theme?
How should this PR be communicated in the release notes?
What does this PR do?
Remove package.json from stable in advance of release. For context, for some reason stable did not have package.json. When we release to npm, package.json gets copied from master into the package. Removing for now so we don't accidentally end up with conflicting package.json when we release since stable has a different structure than the npm package (I had just recently added package.json to stable after an error pulling in that branch to Design System site).
For future, we should revisit the stable branch structure and likely mirror what is in the npm package.
What testing has been done on this PR?
Any background context you want to provide?
What are the relevant issues?
Screenshots (if appropriate)
Is this change backward compatible or could it be a breaking change for the official HPE theme?
How should this PR be communicated in the release notes?