Skip to content

Issues with automated publication #10

@huitseeker

Description

@huitseeker

Some rought spots publishing 0.2.0 with @porcuquine today:

  1. check the cargo release version, folks don’t update this one frequently
  2. the Makefile publishes all tags, that’s not good if the operator’s local tags include those form a remote of the forked project,
  3. the packages are interdependent, so we need to instruct cargo-release on the dependency,
  4. and we probably need some massaging with cargo-release so that the path dependency from bellpepper-core to bellpepper doesn’t prevent the operator from publishing.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions