Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
L
libc
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Issue analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
felixmoebius
libc
Commits
e38ca715
Unverified
Commit
e38ca715
authored
4 years ago
by
Yuki Okushi
Committed by
GitHub
4 years ago
Browse files
Options
Downloads
Plain Diff
Merge pull request #1826 from shepmaster/release-instructions
Remove unneeded release step
parents
b17047fc
11e03e8e
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
CONTRIBUTING.md
+3
-6
3 additions, 6 deletions
CONTRIBUTING.md
with
3 additions
and
6 deletions
CONTRIBUTING.md
+
3
−
6
View file @
e38ca715
...
...
@@ -53,14 +53,11 @@ platform in this crate, the next step is to get that sweet, sweet usage from
crates.io! The only next step is to bump the version of libc and then publish
it. If you'd like to get a release out ASAP you can follow these steps:
1.
Update the version number in
`Cargo.toml`
, you'll just be bumping the patch
version number.
2.
Run
`cargo update`
to regenerate the lockfile to encode your version bump in
the lock file. You may pull in some other updated dependencies, that's ok.
3.
Send a PR to this repository. It should
[
look like this
][
example
]
, but it'd
1.
Increment the patch version number in
`Cargo.toml`
.
1.
Send a PR to this repository. It should
[
look like this
][
example
]
, but it'd
also be nice to fill out the description with a small rationale for the
release (any rationale is ok though!)
4
.
Once merged the release will be tagged and published by one of the libc crate
1
.
Once merged
,
the release will be tagged and published by one of the libc crate
maintainers.
[
example
]:
https://github.com/rust-lang/libc/pull/583
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment