v1.4.1 🌈

Summary

This PR adds a previously missing field 'Author' which the NPM package export can take advantage of to show the developer's name, email, and the URL for the package's website. It also adds the ability to generate packages (legacy Unity packages and NPM style packages) via the command-line, which can be taken advantage of in a continuous integration (CI) process to create packages in an automated way.

ADDED

• Added 'Author' field (with name, email, and URL) to PackageManifestConfig.
• Added CommandLineTools with helper method for retrieving command line arguments.
• Added 'PackageToolsCI' class for use in instrumenting command-line package generation.

CHANGED

• NA

FIXED

• NA

REMOVED

• NA

v1.3.2

ADDED

• Bumped patch version number to rectify incorrectly published package source for v1.3.1

v1.3.0

v1.3.0

ADDED

• Added ability to generate VersionConstants.cs file at desired location and with or without a custom namespace. This is a static class containing versioning and git information about the package and its repository at the time it was created.
• Added additional documentation for VersionConstants generation, excluding files and folders from packages, and an updated screenshot of the PackageManifestConfig inspector. This can be found on the main github page here.

v1.2.0

Overview

This release adds support for exporting the source contents of a PackageManifestConfig as a .UnityPackage file. This makes it easier to be able to create a single file archive that can then be uploaded or sent for a user(s) to import rather than referencing the package in their manifest.json file.

This can be utilized by selecting the Export as Legacy Package button on the PackageManifestConfig inspector.

In addition, this package removes the unit tests from the package source as this can cause errors in newer versions of Unity where NUnit is no longer included with the editor by default and must be included by the user as a package.

There was also some internal refactoring and code cleanup that has no impact on functionality.

Release Notes

• Added support for PackageManifestConfig to export package source as a UnityPackage.
• Internal code cleanup and style refactor.
• Removed unit tests from package; in later versions of Unity nunit functionality is only available through a custom package and this can cause errors if not present. Unit tests are still available in repository.

v1.1.0

Overview

This release adds the ability to exclude files and/or folders from the package export process. This is useful where there may be development-only files, examples, or other meta content such as hidden folders or files like you might find in git submodules that you do not want to include in the exported package contents. This new feature can be found in the same location where package contents are currently configured; the inspector for a PackageManifestConfig asset.

To update this package in an existing project, you can either:

• Release the lock on the package in your manifest.json. This will automatically pull the latest package when focus is switched back to the Unity editor or when its next opened.
• Download and import the UnityPackage attached to this release.

Changelist

• Added ability to exclude files/folders from package export.

v1.0.1 Release

Updated license to properly show on web