- `change` remains mostly the same. The difference now is that we select
the packages that should have the same change log entry. Where we used
to specify `--type none`, we can do `yarn change --empty` instead.
- `publish:beachball` was split into `version:changesets` (for bumping
version numbers) and `publish:changesets` (actually publishing).
We are replacing just-scripts to:
1. Make it easier to add/modify commands as we work with our own tools
2. Remove the confusion from having two Just configs and not consuming
the defined tasks within the scripts package
3. Reduce the overhead of managing transitive (dated) dependencies
`dep-check` is currently depending on `jest-diff` for displaying diffs.
This could potentially conflict with existing dependencies and cause
issues.
We're also pulling in more than 10 MBs worth of dependencies. Bundling
makes this package bigger, but the overall installation size is much
smaller.
We don't publish `rnx-kit-scripts` and are using Yarn workspaces to
consume the package internally within the repository. Since we are using
Yarn Classic, it does not understand `workspace:*` version syntax, which
would've ensured that we will always resolve to a package within the
workspace, but have to rely on `*` or matching exact version number. We
are only using exact version number in one package, but that would've
been enough to trigger an exploit if the version number of
`rnx-kit-scripts` changed for any reason.
To mitigate this, the package has been moved under the `@rnx-kit` scope
to prevent us from consuming malware. I've also made sure that we are
using `*` everywhere, and added a CI step to scan `yarn.lock` for
packages that should've come from the repository. In the future, when we
migrate to npm or some later version of Yarn, we should start using
`workspace:*` instead.
* Move TPN CLI from bin to lib and publish from there.
* Fix TPN CLI path
* Add tasks to download, install, build, and run Go programs as part of the build environment. In each package, Go source is under /go/<project> and binaries are compiled to /bin.
* repalce ?. with equivalent code
* Replace ?. with equivalent code
* fix windows plaform name in go distro list
* fix go executable filename on windows
* Change files
* Change build-tools build output to verbose for CI loops. Doesn't appear to be a way to keep dev builds as warning-only without duplicating preinstall/posinstall commands (which I don't want to maintain).
* separate go task for hello world example
* Add a Go build step to each package build
* Add missing dependency
* Change files
* Move Go infra into its own package so other repos can use it. Add documentation. Remove dependency on just-scripts.
* Change files
* update readme file
* Update packages/go/README.md
Co-authored-by: Lorenzo Sciandra <lsciandra@microsoft.com>
* Update packages/go/README.md
Co-authored-by: Tommy Nguyen <4123478+tido64@users.noreply.github.com>
* Rename package from go to golang. Revert loglevel on yarn build-tools.
* Add handling for non-monorepo cases.
* Update packages/golang/package.json
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Lorenzo Sciandra <lsciandra@microsoft.com>
Co-authored-by: Tommy Nguyen <4123478+tido64@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Rather than having to run `yarn build` or `yarn build-scope` from
workspace root, we can now run `yarn build --dependencies` within any
package. This allows us to stay within the package we're currently
working on.
github-actions[bot]
Lorenzo Sciandra
Tommy Nguyen
React Native Bot
Adam Foxman