fix: set devnet initial version to 0.2.0 for 0.3.0 release

[solidsnakedev]

No description provided.

[Copilot]

Pull request overview

This PR downgrades the @evolution-sdk/devnet package version from 0.2.5 to 0.2.0 in preparation for what the title suggests is a 0.3.0 release. Based on the changeset, this appears to be related to the initial standalone release of the devnet package after extracting it from the main evolution package.

Key Changes:

• Version number changed from "0.2.5" to "0.2.0" in the devnet package

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Downgrading the version from 0.2.5 to 0.2.0 violates semantic versioning principles and could cause issues with package managers. If this package was previously published at 0.2.5, npm will reject publishing a lower version number.

If this is truly an initial standalone release (as suggested by the changeset), consider either:

1. Using a version like 1.0.0 to indicate the first standalone release
2. Continuing from 0.2.5 (or bumping to 0.3.0 as the PR title suggests)
3. If the package was never published before, ensure the npm registry doesn't have any existing versions

The PR title mentions "0.3.0 release" but sets the version to 0.2.0, which appears inconsistent.

Suggested change

	"version": "0.2.0",
	"version": "0.3.0",