chore: bump panda to 2.0.0-beta.17, drop publish workflow

[Adebesin-Cell]

📚 Description

Bumps @pandacss/dev, @pandacss/preset-base, and @pandacss/preset-panda from 2.0.0-beta.15 to 2.0.0-beta.17 across the monorepo and panda-app examples (package.json + lockfiles), and removes the Publish pandacn GitHub workflow since we publish that package locally.

⛳️ Current behavior

Examples pin panda 2.0.0-beta.15, and .github/workflows/publish.yml publishes pandacn from CI on pandacn-v* tags.

🚀 New behavior

Examples pin panda 2.0.0-beta.17. Publishing pandacn is done locally, so the CI publish workflow is removed.

💣 Is this a breaking change?

No.

Confidence Score: 4/5

The dependency upgrade appears sound, but the explicit publishing guidance should be corrected before merging so it does not direct maintainers to a deleted GitHub Action.

Findings

1.  Publishing guidance becomes stale ▶

Fix with agent prompt

### Issue 1
.github/workflows/publish.yml:1-29
Deleting the `Publish pandacn` workflow leaves the repository guide directing maintainers to a GitHub Action that no longer exists. This violates the repository directive that publishing runs through this action or the local command. Update the guide to document the local-only release procedure before merging so contributors are not sent to a dead path.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

This PR upgrades the Panda CSS development and preset packages from 2.0.0-beta.15 to 2.0.0-beta.17 across the monorepo and standalone Panda app, refreshes both lockfiles and their transitive native tooling dependencies, and removes the GitHub-based pandacn publishing workflow.

• Direct Panda dependencies remain version-aligned across each example.
• Lockfiles consistently resolve the upgraded Panda package graph.
• The publishing documentation should be updated for the local-only process.

_{Reviews (1) · Last reviewed commit: "chore: bump panda to 2.0.0-beta.17, drop..."}