Skip to content

cloud setup: pin devkit and mcpls to their plugin versions #98

Description

@AbysmalBiscuit

A cached cloud setup keeps whatever devkit release was latest when the cache was built. The plugin's hooks then call verbs that binary lacks (devkit hook user-prompt-submit fails with unrecognized subcommand 'hook' and blocks every prompt). The plugin bootstrap doesn't repair it: with no stamp, it marks the binary external and never upgrades it.

cloud_setup.py --install should install the devkit and mcpls releases that match their plugin versions, not latest, and write each plugin bootstrap's bootstrap-version stamp. The bootstrap then owns the binaries and upgrades them when the plugin version moves. Installs go to DEVKIT_INSTALL_DIR / MCPLS_INSTALL_DIR, set in the cloud environment, so setup and the bootstrap write to the same place.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions