Skip to content

Commit

Permalink
Release 1.0.0
Browse files Browse the repository at this point in the history
  • Loading branch information
goerz committed Jun 3, 2024
1 parent 09bffa2 commit 5bcdd2b
Show file tree
Hide file tree
Showing 6 changed files with 27 additions and 12 deletions.
19 changes: 10 additions & 9 deletions .github/workflows/CI.yml
Original file line number Diff line number Diff line change
Expand Up @@ -37,10 +37,10 @@ jobs:
arch: x86
steps:
- uses: actions/checkout@v4
- uses: julia-actions/setup-julia@v1
- uses: julia-actions/setup-julia@v2
with:
version: ${{ matrix.version }}
- uses: julia-actions/cache@v1
- uses: julia-actions/cache@v2
- name: "Instantiate test environment"
shell: julia --color=yes --project=test {0}
run: |
Expand All @@ -56,18 +56,19 @@ jobs:
- name: "Summarize coverage"
run: julia --project=test -L devrepl.jl -e 'display(show_coverage())'
- uses: julia-actions/julia-processcoverage@v1
- uses: codecov/codecov-action@v3
- uses: codecov/codecov-action@v4
with:
files: lcov.info
file: lcov.info
token: ${{ secrets.CODECOV_TOKEN }}
testoldest:
name: Test Lower Compat Bounds
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: julia-actions/setup-julia@v1
- uses: julia-actions/setup-julia@v2
with:
version: 1.6
- uses: julia-actions/cache@v1
- uses: julia-actions/cache@v2
- name: "Instantiate test environment"
shell: julia --color=yes --project=test {0}
run: |
Expand All @@ -90,7 +91,7 @@ jobs:
pages: write
steps:
- uses: actions/checkout@v4
- uses: julia-actions/setup-julia@v1
- uses: julia-actions/setup-julia@v2
with:
version: '1'
- name: "Instantiate build environment"
Expand All @@ -106,7 +107,7 @@ jobs:
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
DOCUMENTER_KEY: ${{ secrets.DOCUMENTER_KEY }}
- uses: actions/upload-artifact@v3
- uses: actions/upload-artifact@v4
with:
name: doc-inventories-docs
path: docs/build/
Expand All @@ -115,7 +116,7 @@ jobs:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: julia-actions/setup-julia@v1
- uses: julia-actions/setup-julia@v2
with:
version: '1'
- name: Install JuliaFormatter and format
Expand Down
8 changes: 8 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
# Release Notes

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## Version 1.0.0 - 2024-06-03

* Initial stable release
2 changes: 1 addition & 1 deletion Project.toml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
name = "DocInventories"
uuid = "43dc2714-ed3b-44b5-b226-857eda1aa7de"
authors = ["Michael Goerz <[email protected]>"]
version = "0.4.1"
version = "1.0.0"

[deps]
CodecZlib = "944b1d66-785c-5afd-91f1-9de20f533193"
Expand Down
1 change: 1 addition & 0 deletions docs/make.jl
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,7 @@ GITHUB = "https://github.com/goerz/DocInventories.jl"
links = InterLinks(
"Julia" => (
"https://docs.julialang.org/en/v1/",
"https://docs.julialang.org/en/v1/objects.inv",
joinpath(@__DIR__, "src", "inventories", "Julia.toml")
),
"JuliaDocs" => (
Expand Down
4 changes: 2 additions & 2 deletions docs/src/creating.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Creating Inventory Files

In general, inventory files should be generated automatically by [Documenter](@extref Documenter :doc:`index`) or [Sphinx](@extref sphinx :doc:`index`). However, there are situations where producing and inventory file "by hand" make sense:
In general, inventory files should be generated automatically by [Documenter](@extref Documenter :doc:`index`) or [Sphinx](@extref sphinx :doc:`index`). However, there are situations where producing an inventory file "by hand" make sense:

* A project does not provide an inventory file. Maybe its documentation is entirely in its Github README file.

Expand All @@ -27,7 +27,7 @@ inventory = Inventory(
nothing # hide
```

Then, we can [`push!`](@extref Julia Base.push!) [`InventoryItems`](@ref InventoryItem) for all pages we want to include in the inventory:
Then, we can [`push!`](@extref Julia Base.push!) new [`InventoryItems`](@ref InventoryItem) for all pages we want to include in the inventory:


```@example creating
Expand Down
5 changes: 5 additions & 0 deletions docs/src/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +56,11 @@ to the relevant `Project.toml` file.
Pages = [page for (name, page) in Main.PAGES[2:end]]
```

## Changelog

The `DocInventories` project follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html). You can find a [`CHANGELOG` for versions after `v1.0`](https://github.com/JuliaDocs/DocInventories.jl/blob/master/CHANGELOG.md) online.


## Related Projects

* [Documenter.jl](https://documenter.juliadocs.org/stable/) — The default documentation generator in the [Julia](https://julialang.org) ecosystem. As of version `1.3.0`, `Documenter` automatically generates and deploys a ([Sphinx-format](@ref "Sphinx Inventory Format")) `objects.inv` file that enables linking into a project's documentation.
Expand Down

2 comments on commit 5bcdd2b

@goerz
Copy link
Member Author

@goerz goerz commented on 5bcdd2b Jun 3, 2024

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/108151

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 v1.0.0 -m "<description of version>" 5bcdd2baf9b4e1a828a38549515d0e31fe2f4166
git push origin v1.0.0

Please sign in to comment.