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

Update documenteer[guide] requirement from <1 to <2 #3

Merged
merged 1 commit into from
Jan 19, 2024

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 16, 2024

Updates the requirements on documenteer[guide] to permit the latest version.

Release notes

Sourced from documenteer[guide]'s releases.

1.0.1

Bug fixes

  • In documenteer technote migrate, change the icon for a file deletion event from ❌ to 🗑️.

Other changes

  • Update the migration docs around the migration tool and convert the previous manual migration docs into a reference of the file-by-file changes.

What's Changed

Full Changelog: lsst-sqre/documenteer@1.0.0...1.0.1

Changelog

Sourced from documenteer[guide]'s changelog.

1.0.1 (2024-01-02)

Bug fixes

  • In documenteer technote migrate, change the icon for a file deletion event from ❌ to 🗑️.

Other changes

  • Update the migration docs around the migration tool and convert the previous manual migration docs into a reference of the file-by-file changes.

1.0.0 (2023-12-17)

Backwards-incompatible changes

  • Documenteer now requires Python 3.11 or later.

  • Dependency changes:

    • Pydantic 2.0 or later.
    • Sphinx 7 and later (and docutils 0.20 and later)
    • pydata-sphinx-theme < 0.13 on account of a change in logo path checking (affects user guide projects).
  • Dropped support for the original technote configuration for Documenteer < 1.0. The documenteer.conf.technote configuration now uses the modern platform build with Technote. See new features below for more details.

  • Dropped CLI commands:

    • The refresh-lsst-bib CLI command is removed. Technotes now automatically vendor lsst-texmf's bib files and cache them using documenteer.ext.githubbibcache.
    • The build-stack-docs CLI command is removed and replaced by the stack-docs and package-docs CLIs in Documenteer 0.3.0.
  • The documenteer.conf.pipelines and documenteer.conf.pipelinespkg configuration modules now derive from documenteer.conf.guide. In doing so, the Pipelines documentation configuration works the same as Rubin Guides, but with additional configuration for pipelines-specific Sphinx extensions and other configurations. With this change, the lsst-sphinx-bootstrap-theme is no longer used by Documenteer.

  • The documenteer.sphinxext module has been removed and the existing Sphinx extensions within it are now available from documenteer.ext. It's no longer possible to use documenteer.sphinxext to automatically load all Documenteer Sphinx extensions. Extensions need to now be added individually to the extensions configuration variable in conf.py. The migrated extension modules are:

    • documenteer.ext.bibtex
    • documenteer.ext.jira
    • documenteer.ext.lsstdocushare
    • documenteer.ext.lssttasks
    • documenteer.ext.mockcoderefs
    • documenteer.ext.packagetoctree

New features

  • All-new technote configuration for Rubin Observatory. Technotes are now built with a framework we created by the same name, Technote. The new technotes feature a responsive design, better on-page navigation, and overall cleaner design that matches Rubin Observatory's visual identity. For authors, technotes use a new configuration file, technote.toml, which replaces metadata.yaml. Technotes can also be written in Markdown (in addition to continuing reStructuredText support) thanks to MyST Parser. Other key features:

    • You can migrate your existing technote by running the documenteer technote migrate CLI command. The migration process is explained in detail at https://documenteer.lsst.io/technotes/migrate.html.

    • Rubin technotes automatically use the bib files from https://github.com/lsst/lsst-texmf. In your text, use the :cite: directive with a bibkey from those bib files to cite a reference. Documenteer automatically retrieves the bib files from GitHub so you no longer need to maintain a copy in your repository.

    • Rubin technotes include a richer metadata base than the original technote system. This will make it easier to cite technotes. Part of the richer metadata system is the authors table in technote.toml files. This author information is derived from, and synchronized with, the authordb.yaml file in lsst/lsst-texmf. The documenteer technote add-author and documenteer technote sync-authors CLI commands can help you manage author information in your technote.

... (truncated)

Commits
  • 343f644 Merge pull request #210 from lsst-sqre/u/jonathansick/1.0.1
  • 4b2c723 Update change log for 1.0.1 release
  • 42c8f66 Merge pull request #204 from lsst-sqre/u/neophile
  • 0814779 Reformat files with black 24.1a1
  • 6c0136f [neophile] Update dependencies
  • a29caed Merge pull request #209 from lsst-sqre/u/fe/3
  • 0420895 Change file deletion icon to trashcan
  • df87f70 Merge pull request #208 from lsst-sqre/u/fe/1
  • 6b944fd Orient migration docs around automated tool
  • bea3adb Merge pull request #207 from lsst-sqre/tickets/DM-42142
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code labels Jan 16, 2024
@afausti
Copy link
Member

afausti commented Jan 19, 2024

@dependabot rebase

Updates the requirements on [documenteer[guide]](https://github.com/lsst-sqre/documenteer) to permit the latest version.
- [Release notes](https://github.com/lsst-sqre/documenteer/releases)
- [Changelog](https://github.com/lsst-sqre/documenteer/blob/main/CHANGELOG.md)
- [Commits](lsst-sqre/documenteer@0.1.0...1.0.1)

---
updated-dependencies:
- dependency-name: documenteer[guide]
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/pip/documenteer-guide--lt-2 branch from df0fc35 to c562299 Compare January 19, 2024 20:47
@afausti afausti merged commit 1448fc0 into main Jan 19, 2024
5 checks passed
@dependabot dependabot bot deleted the dependabot/pip/documenteer-guide--lt-2 branch January 19, 2024 20:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file python Pull requests that update Python code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant