Skip to content

Releases: timonmasberg/nx-migration-gh-action

v1.1.13

16 May 14:04
dece379
Compare
Choose a tag to compare

What's Changed

  • add --if-exists flag to migrate command by @nikolay-karadzhov in #128

New Contributors

  • @nikolay-karadzhov made their first contribution in #128

Full Changelog: v1.1.12...v1.1.13

v1.1.12

20 Dec 09:06
Compare
Choose a tag to compare

Remove legacy peer deps option due to issues with package-lock generation.
Installs packages after migrations with package lock only flag to sync deps.

Full Changelog: v1.1.11...v1.1.12

v1.1.11

19 Dec 00:42
Compare
Choose a tag to compare

Running npm ci before migrating to hopefully fix missing deps issue

Full Changelog: v1.1.10...v1.1.11

v1.1.10

15 Dec 17:36
88fcd2d
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.1.9...v1.1.10

v1.1.9

12 Dec 14:52
dd2a747
Compare
Choose a tag to compare

What's Changed

  • respect the base parameter when creating a PR by @hukuuu in #114

New Contributors

Full Changelog: v1.1.8...v1.1.9

v1.1.8

10 Nov 13:54
Compare
Choose a tag to compare

Tries to fix double installation of dependencies with correct env flag.

v1.1.7

04 Nov 15:21
Compare
Choose a tag to compare

Fixes package lock fuck-ups by nx by skipping duplicate npm install while running the migrations.

Full Changelog: v1.1.6...v1.1.7

v1.1.6

23 Sep 08:45
Compare
Choose a tag to compare

Removes Release notes from PR body since they include contributor tags now.

v1.1.5

01 Aug 11:15
Compare
Choose a tag to compare

Try running npm i after migrations to fix fucked up package lock due to nx migration scripts.

v1.1.4

03 Jul 11:24
Compare
Choose a tag to compare

Fixes an issue where the package lock was in an inconsistent state due to the NX own npm install routine during migrations. Now, after migrations, npm i --package-lock-only will run to ensure package-lock is in a correct state.