package-dependency-tree-upgrade

To track dependency upgrades and Jira blockers, you can audit a project's lockfile to find packages supporting the current framework version but not the next. The tool then cross-references a Jira epic, creates missing tickets, and links them as blockers to establish the correct upgrade order.

Mapping inter-package dependencies to determine upgrade order involves parsing a lockfile to assess package constraints against the next framework version. The tool maps these relationships and automatically sets up corresponding Jira tickets as blockers to enforce the correct sequence.

Yes, you can automatically create Jira tickets for unsupported packages by providing a lockfile path, package prefixes, and framework versions. The tool cross-references existing Jira epics and creates missing tickets for packages lacking next version support.

To audit a lockfile and generate Jira upgrade tickets, you need a project lockfile, package prefixes, the framework package name, current and next version numbers, and Jira connection details. The tool uses these inputs to filter packages and orchestrate ticket creation.

The tool works with any project that has a known framework package and a dependency lockfile. It filters packages by specified prefixes to assess current versus next version support, ensuring structured tracking in Jira for compatible and incompatible dependencies.