Component versions

Component versioning allows you to manage different versions of coded components in your WeWeb project, ensuring stability while enabling updates when needed.

Accessing component versions

To view and manage component versions:

1. Click on the Development icon (terminal icon) in the Interface section sidebar
2. Under the Advanced section, click Component versions

This opens a panel showing all coded components in your project and their current versions.

Understanding component versions

Each coded component in your project has:

• Current version — The version currently installed in your project
• Available versions — Other versions that can be installed
• Version information — Release notes and changes for each version

Version information

For each component version, you can see:

• Version number — Typically follows semantic versioning (e.g., 1.2.3)
• Release date — When the version was published
• Changes — What's new or fixed in this version
• Breaking changes — Changes that may affect existing implementations

Updating component versions

To update a component to a newer version:

1. Open the component versions panel
2. Find the component you want to update
3. Review the available versions and their release notes
4. Select the version you want to install
5. Confirm the update

WARNING

Before updating components:

• Review the release notes for breaking changes
• Test your application in preview mode after updating
• Check that all instances of the component still work as expected

Version strategies

Staying current

Updating to the latest version provides:

• New features and improvements
• Bug fixes and security patches
• Better performance
• Access to latest capabilities

Maintaining stability

Keeping older versions may be necessary when:

• The component works perfectly for your needs
• Newer versions introduce unwanted changes
• You need time to test before upgrading
• Your project relies on specific version behavior

Rollback options

If an update causes issues:

1. Open the component versions panel
2. Select the previous version that worked correctly
3. Reinstall that version
4. Test to confirm the issues are resolved

TIP

Before major updates, note which version you're currently using. This makes it easier to rollback if needed.

Component dependencies

When updating components, consider:

• Dependency compatibility — Some components depend on others
• Integration requirements — Components may require specific integrations
• WeWeb version — Newer component versions may require a recent WeWeb editor version

WeWeb will warn you about incompatibilities before allowing an update.

Version notifications

WeWeb notifies you when:

• New versions of components are available
• Critical security updates are released
• Breaking changes are introduced

You can choose when to apply these updates based on your project timeline.

Best practices

For production projects

• Test updates in a development environment first
• Update components during low-traffic periods
• Review release notes thoroughly before updating
• Keep a backup of your project before major updates
• Monitor your application after updates

For development projects

• Stay more current with component versions
• Test new features as they're released
• Provide feedback to component developers
• Report bugs or issues you encounter

Semantic versioning

Most components follow semantic versioning:

• Major version (1.x.x) — Breaking changes that may require code updates
• Minor version (x.1.x) — New features that are backward-compatible
• Patch version (x.x.1) — Bug fixes and minor improvements

Understanding this helps you assess the risk of updating.

TIP

Minor and patch updates are generally safe to apply, while major version updates require more careful testing.

Managing multiple projects

When using the same component across multiple projects:

• Different projects can use different versions
• Update each project independently based on its needs
• Use consistent versions across related projects when possible
• Document which versions are used where

Automated updates

Some component updates can be configured to:

• Apply automatically for patch versions
• Notify you but require manual approval for minor versions
• Always require manual approval for major versions

Check with your workspace administrator for update policies.

CONTINUE LEARNING

Learn about other development tools and settings:

Learn about show dev information →