Migration

This guide provides instructions for migrating between major versions of PackShip. Each major version may introduce breaking changes that require updates to your project.

Migrating from v1.x to v2.x

Version 2.0 of PackShip marks a significant transition from a commercial product to an open-source project. This change was made to foster community-driven innovation, improve accessibility, increase transparency, and provide educational resources for developers.

Key Changes in v2.x

The primary changes in v2.x focus on:

• Licensing: PackShip is now fully open source, removing all commercial licensing restrictions
• Publishing Improvements: Resolved edge cases and improved reliability in the package publishing process
• Community Focus: Added infrastructure for community contributions and feedback

Update PackShip CLI

To migrate to v2.x, update the PackShip CLI to the latest version:

npm install -g packship@latest

Getting Involved

As an open-source project, PackShip now welcomes community contributions. You can get involved by:

• Starring and watching the GitHub repository
• Providing feedback through GitHub issues
• Contributing code, documentation, or ideas
• Spreading the word about PackShip in your developer communities

Future Plans

The open-source journey for PackShip is just beginning. The roadmap for future versions includes:

• PackShip Pug: A desktop GUI application for visual package management
• Enhanced Plugin System: For extending functionality with community-developed plugins
• Framework Integrations: Better integration with popular frameworks and tools
• Improved Documentation: Expanded learning resources and examples

Getting Help

If you encounter issues during migration or have questions about PackShip v2, you can:

• Check the GitHub issues for similar problems and solutions
• Join the PackShip Discord community for real-time help
• File a new issue on GitHub if you believe you've found a bug