Skip to content

Our internal packages don't respect SemVer 'no leading zeros' #672

@ascjones

Description

@ascjones

I just updated to 31.7 and our internal package versioning is not compatible with it, since we (incorrectly) have leading zeros as version part names.

3486c26

I can potentially fix this but it will take a while for the changes to propogate into our feed and across projects.

So I can tell people to stick on 31.6 until all our packages have removed the leading zeros, or we could add some kind of 'non-strict' semver option?

I suppose it's good to force us to be SemVer compatible, at the cost of some pain and management in the meantime. But on the other hand it might be nice not to break paket if you have any packages in the feed which don't respect SemVer 100%?

Not sure which approach is best - ideas?

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