Skip to content

Commit

Permalink
Add a changelog and prepare for registration
Browse files Browse the repository at this point in the history
  • Loading branch information
JamesWrigley committed Jan 28, 2024
1 parent db00b66 commit 3c51f30
Show file tree
Hide file tree
Showing 6 changed files with 31 additions and 5 deletions.
1 change: 1 addition & 0 deletions docs/.gitignore
Original file line number Diff line number Diff line change
@@ -1,3 +1,4 @@
build/
site/
src/examples.md
src/generated_changelog.md
1 change: 1 addition & 0 deletions docs/Project.toml
Original file line number Diff line number Diff line change
@@ -1,4 +1,5 @@
[deps]
Changelog = "5217a498-cd5d-4ec6-b8c2-9b85a09b6e3e"
Documenter = "e30172f5-a6a5-5a46-863b-614d45cd2de4"
LibSSH = "00483490-30f8-4353-8aba-35b82f51f4d0"
Literate = "98b081ad-f1c9-55d3-8b20-4c87d4299306"
Expand Down
10 changes: 10 additions & 0 deletions docs/make.jl
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
import Revise
import Literate
import Changelog
import Documenter
import Documenter: Remotes, makedocs, deploydocs

Expand Down Expand Up @@ -63,6 +64,14 @@ Literate.markdown(joinpath(@__DIR__, "src/examples.jl"),
execute=true,
flavor=Literate.DocumenterFlavor())

# Build the changelog
Changelog.generate(
Changelog.Documenter(),
joinpath(@__DIR__, "src/changelog.md"),
joinpath(@__DIR__, "src/generated_changelog.md"),
repo="JamesWrigley/LibSSH.jl"
)

# Build and deploy the docs
makedocs(;
repo = Remotes.GitHub("JamesWrigley", "LibSSH.jl"),
Expand All @@ -78,6 +87,7 @@ makedocs(;
"server_support.md",
"utilities.md",
"bindings.md",
"generated_changelog.md",
"contributing.md"
],
modules = [LibSSH],
Expand Down
14 changes: 14 additions & 0 deletions docs/src/changelog.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
# Changelog

This documents notable changes in LibSSH.jl. The format is based on [Keep a
Changelog](https://keepachangelog.com).

## [v0.1.0] - 2024-01-28

The initial release 🎉 ✨

### Added

- Basic client support, and high-level wrappers for some [Channel
operations](@ref).
- A [Demo server](@ref) for testing SSH clients.
6 changes: 3 additions & 3 deletions docs/src/contributing.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,9 +34,9 @@ Here's a suggested workflow if you're writing documentation:
```julia-repl
pkg> activate docs
julia> using LiveServer
# Skip monitoring examples.md because that's generated automatically, otherwise
# we'd get into an infinite loop.
julia> servedocs(; include_dirs=["src"], skip_files=["docs/src/examples.md"])
# Note that we ignore automatically generated files, otherwise we'd end up in an
# infinite loop.
julia> servedocs(; include_dirs=["src"], skip_files=["docs/src/examples.md", "docs/src/generated_changelog.md"])
```

This will start a server with
Expand Down
4 changes: 2 additions & 2 deletions docs/src/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,9 +25,9 @@ ssh.lib_version()

## Installation

LibSSH.jl isn't registered yet, so for now you'll have to add it from Github:
LibSSH.jl is available in the general registry:
```julia-repl
pkg> add https://github.com/JamesWrigley/LibSSH.jl
pkg> add LibSSH
```

## Limitations
Expand Down

2 comments on commit 3c51f30

@JamesWrigley
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@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/99723

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.1.0 -m "<description of version>" 3c51f30cc04ffa38a3962543618bab207f29b1e7
git push origin v0.1.0

Please sign in to comment.