Skip to content

Commit

Permalink
Update Project.toml
Browse files Browse the repository at this point in the history
  • Loading branch information
tlienart authored Nov 13, 2020
1 parent 308ec70 commit b20a755
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion Project.toml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
name = "RDatasets"
uuid = "ce6b1742-4840-55fa-b093-852dadbb1d8b"
version = "0.6.10"
version = "0.7.0"

This comment has been minimized.

Copy link
@tlienart

tlienart Nov 13, 2020

Author Collaborator

[deps]
CSV = "336ed68f-0bac-5ca0-87d4-7b16caf5d00b"
Expand Down

5 comments on commit b20a755

@JuliaRegistrator
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Registration pull request created: JuliaRegistries/General/24571

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.7.0 -m "<description of version>" b20a755177647e2f60baae2557e4118c5c343e28
git push origin v0.7.0

@nalimilan
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tlienart Why did you tag a breaking version? There don't appear to be any breaking changes since last release. This requires updating version bounds in all dependencies, which can be painful (e.g. GiovineItalia/Gadfly.jl#1499).

@tlienart
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nalimilan apologies for the nuisance, since no one maintains this package afaik but that a number of packages depend on it I thought it was less risky to do a minor release with the recent addition of datasets + bump of CSV since the PR merge required marking some tests as broken #102.

Anyway I guess here the right route would have been to not merge the PR and leave things as they were. Again apologies for that.

@nalimilan
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How did that PR end up being merged while not even passing CI? Marking these tests as broken is just a bandaid, and making a release with broken tests is far from ideal.

@tlienart
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's just the list of dataset that's not been updated... I'll try to fix that myself.

Please sign in to comment.