Tool to pull atlaskit version history from a repo
yarn add @atlaskit/dependency-version-analytics8dd71b2e0653 - Updated bin property to string as the package name and bin name matches. https://yarnpkg.com/configuration/manifest#bin1cb2b8f4e1d7 - Take subWorkDir into consideration when checking for root package.json changesf602c4298340 - Migrate @atlaskit/dependency-version-analytics to use declarative entry pointsd23cb258eb0 - Using flags.cwd to set current workDir and use package.json from current workDir instead of root27db2e84c40 - Removing '--current' postfix from packageName before checking it for support3fb20c4aeba - Add postinstall check to enforce internal peer dependencies7913f15625c - Upgraded @atlassiansox/analytics-node-client from 2.2.1 to 3.2.1ec86e718ae9 - Upgrade internal dependency @atlassiansox/analytics-node-client to fix a bug when bundling the analytics clienta424e62b264 - Changes to support Node 16 Typescript definitions from @types/node.#18668 bca63cdea49 - Remove url-parse
We should use browser built-ins not url-parse
#7071 98deccc667 - Add support for repositories using yarn workspaces
Upgrade events are sent for dependencies listed in any declared workspace, not only the root package.json. An upgrade event is only sent when all workspaces move to a new version. The lowest semver version across the repo is used as the aggregated version of a dependency.
b3d3b36c06 - Add statlas flag that uploads last run state to statlas rather than a git tag3f51c7d0b8 - Fix versionString not including version range or prerelease info#6631 c8a5330883 - Fix custom jira suffixed dependencies used for independent upgrades.
'--current' suffixed deps are now treated as normal deps and converted to a non-suffixed name and proper version. '--next' deps are ignored. upgradeType is now also fixed to reflect the 'upgrade' upgradeType rather than 'add' and 'remove'.
26c63f4bc3 - Fix dependency type changes not being sent as separate remove/add events
When a dependency changes type, e.g. dependencies to devDependencies, we need to record it as separate remove & add events so that our queries can easily tell that the package is no longer a normal dependency. This is even a bigger problem when a dependency changed dependency type without any version change as no event would be sent at all in that case.
7ef9198547 - Update dependency name & version to take into account --next and --current.5f58283e1f - Export types using Typescript's new "export type" syntax to satisfy Typescript's --isolatedModules compiler option.
This requires version 3.8 of Typescript, read more about how we handle Typescript versions here: https://atlaskit.atlassian.com/get-started
Also add typescript to devDependencies to denote version that the package was built with.#3885 6c525a8229 - Upgraded to TypeScript 3.9.6 and tslib to 2.0.0
Since tslib is a dependency for all our packages we recommend that products also follow this tslib upgrade to prevent duplicates of tslib being bundled.
[patch]da71912521:
ED-8822 fix: readd @atlassiansox/analytics-node-client as peer dependency
[patch]5ccd5d5712:
ED-8822: promote internal packages from peer to automatically installed dependencies
[patch]a1bc1e6637:
AFP-1437: Fix vulnerability issue for url-parse and bump to ^1.4.5.Packages.
[patch]6548261c9a:
Remove namespace imports from React, ReactDom, and PropTypes
[patch]a2d0043716:
Updated version of analytics-next to fix potential incompatibilities with TS 3.6
[patch]097b696613:
Components now depend on TS 3.6 internally, in order to fix an issue with TS resolving non-relative imports as relative imports
[patch]b9b8222978:
@types/node-fetch was declared in devDependencies and dependencies. Move @types/node-fetch, @types/node, @types/url-parse from dependencies to devDependencies.
[patch]620613c342:
Fix regression in populate-package where new packages would throw an error
[patch]10b3af15f6:
Fix version.json (cli version in analytics) being one version behind
[patch]50ddd93885: