Skip to content

Settings and activity

2 results found

  1. 5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Sean O'Connor supported this idea  · 
  2. 12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Sean O'Connor supported this idea  · 
    An error occurred while saving the comment
    Sean O'Connor commented  · 

    This causes problems with gitflow releases as well. On a gitflow finish release, it first merges the release to the develop branch, before merging it to master. So Appveyor (our CI), which builds on commit, builds 1.1-preview.10 from dev first before building 1.0 from master, which screws up our dev environment.

    If this were simply ordered by semver like it is in the Library->Packages view (or at least make that an option) this wouldn't wouldn't be an issue.