Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wasmer deploy fails with named local package and rejected package bump #4707

Open
theduke opened this issue May 16, 2024 · 1 comment
Open
Assignees
Labels
bug Something isn't working edge-cli

Comments

@theduke
Copy link
Contributor

theduke commented May 16, 2024

Describe the bug

Can't deploy with local named package without a version bump.

Steps to reproduce

wasmer.toml:

[package]
name = "wasmer-tests/static-site"
version = "0.1.0"
description = "wasmer-tests/static-site website"

[dependencies]
"wasmer/static-web-server" = "^1"

[fs]
public = "public"

app.yaml:

name: xxx
owner: xxx
package: .
kind: wasmer.io/App.v0
  • wasmer deploy
  • Do you want to bump the package? => SELECT NO

=> ERROR

 endpoint=https://registry.wasmer.io/graphql
error: GraphQL query failed
╰─▶ 1: GraphQL API failure: This version of the package `wasmer-tests/static-site@0.1.0` already exists.

Expected behavior

Command does not try to re-publish, but just uses the existing version.

Actual behavior

Tries to republish, fails.

@theduke theduke added bug Something isn't working edge-cli labels May 16, 2024
@syrusakbary
Copy link
Member

Use case: a user has a named package, and want to publish (for testing) an unnamed package meanwhile (before bumping the version)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working edge-cli
Projects
None yet
Development

No branches or pull requests

3 participants