This is one in a series of PRs to rename current packages that are only
published to our internal npm feeds to use the @fluid-private scope.
This PR covers the following fluid-internal packages:
- test-dds-utils
- test-loader-utils
This is one in a series of PRs to rename current packages that are only
published to our internal npm feeds to use the \@fluid-private scope.
This PR covers the following fluid-internal packages:
- test-version-utils
- test-pairwise-generator
This is one in a series of PRs to rename current packages that are only
published to our internal npm feeds to use the @fluid-private scope.
This PR covers the following fluid-internal packages:
- stochastic-test-utils
- test-drivers
Uses the --outFile argument instead of console redirect so the output
files doesn't get overwritten if there is an error.
---------
Co-authored-by: Tyler Butler <tyler@tylerbutler.com>
This is one in a series of PRs to rename current packages that are only
published to our internal npm feeds to use the @fluid-private scope.
This PR covers the following fluid-internal packages:
- @fluid-internal/test-end-to-end-tests
As we add/remove/move packages, these lists will change and we can use
them to verify _before we run the publishing pipeline_ what will be
published. The CI pipeline just publishes the packages in each list to
the feed in question. This makes it far less likely that we find out a
package is missing in a feed only after we do a release.
They are generated by running the `generate:packageList` script from the
root of the release group. They are also generated during a build, so
these files are kept up-to-date as changes are made.
Matt Rakow
Tyler Butler
Curtis Man