Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Releases #94

Open
kaarthiksundar opened this issue Apr 29, 2019 · 33 comments
Open

Releases #94

kaarthiksundar opened this issue Apr 29, 2019 · 33 comments

Comments

@kaarthiksundar
Copy link
Collaborator

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/421

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

git tag -a v0.3.5 -m "<description of version>" 2de66f3a1d5e9939a75514abcacd0535b88d4ae1
git push origin v0.3.5

@pseudocubic
Copy link
Collaborator

@kaarthiksundar for the future, I found you can comment on a commit (see lanl-ansi/ThreePhasePowerModels.jl@97423d2#comments) instead of making an issue

@ccoffrin
Copy link
Member

Cool!

@kaarthiksundar
Copy link
Collaborator Author

@pseudocubic What is this requirement the moderator is talking about in JuliaRegistries/General#421

@ccoffrin
Copy link
Member

The remark is that you dropped a number of version requirements on package dependencies. You should visit your [compat] block and make sure it is accurate.

@pseudocubic
Copy link
Collaborator

I think it's because there used to be version requirements for JSON and MathProgBase, but we didn't add those to the compat section, my guess is because we had assumed that the julia and JuMP dependencies would implicitly restrict those versions.

@ccoffrin
Copy link
Member

ccoffrin commented Apr 30, 2019

If your code loads a package, its best practice to put at least a version lower bound on that package. This used to be enforced by the Julia ecosystem managers.

@kaarthiksundar
Copy link
Collaborator Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/786

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 Julia TagBot is installed, or can be done manually through the github interface, or via:

git tag -a v0.3.6 -m "<description of version>" 00a2118bdd79f59e993bdb0b9f0e14ce89137ce7
git push origin v0.3.6

@kaarthiksundar
Copy link
Collaborator Author

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/787

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 Julia TagBot is installed, or can be done manually through the github interface, or via:

git tag -a v0.4.0 -m "<description of version>" 761e9b43704d6f2b73f8e444f63f2a1ca5a5542e
git push origin v0.4.0

@ccoffrin
Copy link
Member

v0.4.1
@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/1591

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 Julia TagBot is installed, or can be done manually through the github interface, or via:

git tag -a v0.4.1 -m "<description of version>" cf8237b744798fdda392173151f4826ef962d23e
git push origin v0.4.1

@pseudocubic pseudocubic changed the title Register Registrator Releases Feb 26, 2020
@pseudocubic
Copy link
Collaborator

v0.6.0
@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/10146

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 Julia TagBot is installed, or can be done manually through the github interface, or via:

git tag -a v0.6.0 -m "<description of version>" fa867581e7442ca4373db0b29934a935e50a30d4
git push origin v0.6.0

@pseudocubic
Copy link
Collaborator

v0.6.0
@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request updated: JuliaRegistries/General/10146

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 Julia TagBot is installed, or can be done manually through the github interface, or via:

git tag -a v0.6.0 -m "<description of version>" b1cf5a6f46cccf295ccf876023cac515037007af
git push origin v0.6.0

@pseudocubic
Copy link
Collaborator

v0.7.0
@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/14684

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>" e050764ffe78dc76c562d113a633ffa62280549c
git push origin v0.7.0

@pseudocubic
Copy link
Collaborator

v0.7.0
@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request updated: JuliaRegistries/General/14684

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>" 950a3b5af24e3bda2945dce0d7140bc703d5685b
git push origin v0.7.0

@tasseff
Copy link
Member

tasseff commented Mar 2, 2021

v0.9.0
@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/31156

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.9.0 -m "<description of version>" 5b5f62c0ab3b540926dbfce603be28f9730e4573
git push origin v0.9.0

@kaarthiksundar
Copy link
Collaborator Author

v0.9.1
@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/57169

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.9.1 -m "<description of version>" 8fd64a2ca4ed1a4148d015807f3b3b9f4222c00a
git push origin v0.9.1

@kaarthiksundar
Copy link
Collaborator Author

v0.9.2
@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/64971

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.9.2 -m "<description of version>" 099e4dbc94b693e632226bae14326448ef82df7b
git push origin v0.9.2

@ccoffrin
Copy link
Member

v0.9.3
@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/99882

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

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.9.3 -m "<description of version>" ec7fe88af9b83be820e4d020186dd5a09241d134
git push origin v0.9.3

@ccoffrin
Copy link
Member

v0.9.3 second try
@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request updated: JuliaRegistries/General/99882

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

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.9.3 -m "<description of version>" 70ae501314ce66b091d888b6a5a96d5a4d2d4b2d
git push origin v0.9.3

@ccoffrin
Copy link
Member

v0.10.0
@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/99924

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

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.10.0 -m "<description of version>" 7a0dc258db40cb6351e4e07d7be1494b3544c639
git push origin v0.10.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants