CHANGELOG.md

Change Log

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog and this project adheres to Semantic Versioning

[9.7.0] 2026-09-08

Changed

• the copier-update skill warns that a merge can be wrong without raising a conflict, and says how to check
  • a template change can fail to arrive, and a project's own configuration can be replaced by the template's - both silently, so "no conflicts" does not mean "nothing to review"
• plugin: the plugin-implementation skill says to set plugin_id explicitly, and both example plugins now do - the generated default embeds the module path and class name, so moving or renaming a module changes the identity of a deployed task and orphans the workflow tasks referencing it
  • a project adopting this for a task that is already deployed has to write down the identifier it generates today, verbatim; a tidier one breaks exactly what setting the field protects (#91)
• plugin: the plugin-implementation skill says what execute() is handed, not only what a task declares - a workflow can never deliver more inputs than the declared ports, but a port left unconnected is absent from the sequence rather than empty
  • a task guarding against surplus inputs is guarding against a state the workflow editor cannot produce, and must not warn its users about one (#89)

[9.6.1] 2026-09-06

Fixed

• the Stop hook only reports a rule that really joined [tool.ruff.lint] ignore, and names it
  • it matched any quoted rule code anywhere in pyproject.toml, so extend-select, a [tool.deptry] entry and the per-file-ignores relaxation the shipped rules prescribe all blocked a session
• plugin: the plugin-implementation skill separates port arity (FixedNumberOfInputs) from port schema (FixedSchemaPort, FlexibleSchemaPort, UnknownSchemaPort) - the warning about flexible input schemas named only the first, so it read as not applying to FixedNumberOfInputs([FlexibleSchemaPort()])
• plugin: the example workflow plugin declares its ports, which the skill beside it says not to leave implicit

[9.6.0] 2026-09-06

Changed

• the preparation YAML anchor of the generated Taskfile.yaml is replaced by two internal tasks, prepare and package:exists
  • a merge key is silently dropped by any task that declares deps of its own, which is how build came to run without poetry:install
• neither format task depends on poetry:install any more (#81)
  • poetry install refuses to run against a stale lock file, which stopped the PostToolUse hook formatting anything for the rest of a session
  • on a clone with no virtualenv yet, run task check or task poetry:install before formatting
• the Stop hook runs .claude/hooks/template-feedback.py directly instead of through task, whose output would corrupt the hook's JSON channel on stdout (#81)
• the shipped .claude/rules/ tells an agent not to cite an issue or Jira ticket in a project's changelog, since the people reading it cannot open them
• plugin: the plugin-implementation skill documents ports that depend on a parameter's value - the standard way to offer a parameter and a connected input as mutually exclusive alternatives, rather than accepting both and choosing at runtime (#78)
• plugin: the plugin-implementation skill prefers fixed schema ports, and names the array assignment index out of range: 0 abort that a flexible input schema can cause when the operator is fed by a file dataset (#79)

Removed

• the template:feedback-check and check:prepare tasks of the generated Taskfile.yaml
  • nothing calls either: the Stop hook runs its script directly, and prepare does what check:prepare did
  • a TaskfileCustom.yaml naming check:prepare as a dependency has to be updated; the hand run of the hook is echo '{}' | python3 .claude/hooks/template-feedback.py

Fixed

• the Stop hook of a generated project looks at the right evidence (#80)
  • it no longer blocks on the conflict-marker example inside its own copier-update skill, on a project that has not committed yet, or on a changelog entry that merely names # noqa
  • it now sees a suppression added in an untracked file, and ignores one that was already there
  • git output is parsed in a pinned format, so diff.noprefix, core.quotePath or an untracked directory can no longer hide evidence
• task check can no longer pass without having looked at the package (#83)
  • PACKAGE is a shell expansion, so an exported package_dir outranks the .copier-answers.env entry - and an empty one dropped the package from every command line while the checks still reported success
  • package:exists now fails when the name does not resolve to a directory
• build depends on poetry:install again (#82)
  • plugin: task install builds and then runs poetry run cmemc, which failed on a fresh clone because no virtualenv had been created
• an empty [tool.pytest.ini_options] table is back in the generated pyproject.toml, so a pytest.ini, tox.ini or setup.cfg above the project can no longer take over its rootdir or inject addopts into its suite (#85)
• github: check.yml declares a least privilege permissions: block, and its two reporting steps are continue-on-error, so a pull request from a fork no longer reds the whole check on a token it cannot be given (#84)
• github: xportation/junit-coverage-report is pinned to v1.0.3 rather than the mutable @main - the same commit today, so the step does not change (#84)

[9.5.0] 2026-09-02

Changed

• plugin: the plugin-testing skill now says how to name an environment variable that a test introduces for an external system: TESTING_<SERVICE>_<THING>, gated with the same skipif pattern as needs_cmem
  • the prefix is what separates, in a .env file or a group level list of CI variables, the entries that drive the test suite from those that configure the product
  • the eccenca Corporate Memory connection variables are named as the exception: CMEM_BASE_URI and the OAUTH_* trio keep their established cmemc names, because the plugin and cmemc read them too

[9.4.0] 2026-08-27

Changed

• the LICENSE of a generated project now names that project's own copyright holder, rendered from the author_name answer, instead of the hardcoded Copyright 2021 CMEM every project inherited unchanged
  • the year is dropped rather than templated: copier cannot compute one without the deprecated jinja2-time extension, and a fixed 2021 is wrong for every project generated since
  • existing projects see the line change on their next copier update
• plugin: the plugin-documentation skill now states how the product is named in user-visible text: eccenca Corporate Memory on the first mention of each block, plain "Corporate Memory" afterwards, never "CMEM", identifiers exempt
  • the shipped prose follows it: the README-public.md sentence is now a single [eccenca Corporate Memory] link rather than two links splitting the name, and the sample skipif reason reads Needs eccenca Corporate Memory configuration
  • projects that answer pypi carry the README-public.md wording onto their public package page, so this is visible on the next release
• plugin: the logging example in the agent guidance now uses an f-string
  • it showed the logging idiom self.log.info("...%s...", count), which raises TypeError: self.log is a PluginLogger, whose methods take a single already formatted string, not a format string plus arguments
• plugin: agent guidance now names get_client(context) as the way to reach a deployment, instead of Client.from_context(context=context)
  • the two are the same call - get_client() adds a UserContext guard and is reached through cmem-plugin-base, which every plugin already depends on
  • the guidance says explicitly that existing Client.from_context() calls are correct and must not be rewritten, since that direction is the one that drops the guard

[9.3.0] 2026-08-23

Changed

• .gitignore now says what a project does with .idea/, following github/gitignore

  • only the machine specific parts are ignored - workspace.xml, tasks.xml, usage.statistics.xml, dictionaries, shelf, the data source files - plus misc.xml, which names the local Python interpreter, and .idea/sonarlint/, whose binary index files neither that list nor PyCharm covers
  • vcs.xml, modules.xml, the project .iml, inspectionProfiles/ and runConfigurations/ stay shared, which is what PyCharm's own generated .idea/.gitignore already assumes: they describe the project, not the machine
  • until 8.8.0 an unanchored *.xml pattern hid all of these; removing it left them untracked, so your first update may show a handful of new untracked .idea files - committing them once is the intended resolution, and it makes the project's inspection profile and run configurations available to everyone who opens it
  • nothing is untracked by this: ignoring never removes a file git already follows

• plugin: the plugin-implementation skill says how a task constructor answers PLR0913 and PLR0917

  • a constructor takes one argument per PluginParameter, so its arity follows the task's configuration surface and neither of ruff's escapes is available: keyword-only arguments change the signature DataIntegration instantiates, and folding parameters into an object breaks the one-argument-per-parameter mapping
  • PLR0917 became stable in ruff 0.16, so a task with six or more parameters can start failing task check without anything in the task having changed - the projects that already carry # noqa: PLR0913 there need the code widened to # noqa: PLR0913, PLR0917
  • it stays out of the ignore list in pyproject.toml on purpose, since it is a real finding on an ordinary function

[9.2.1] 2026-08-23

Fixed

• the session end check no longer reports a copier update through its content signals either
  • 9.2.0 stopped the update tripping the changed-files signal, but the # noqa signal read the same diff and matched the template's own prose about # noqa - so updating to 9.2.0 was reported by the very text that fixed the previous round of this
  • diff lines are now attributed to their file, and a suppression inside a template owned file is ignored: it was written by the template, so it can never be this project working around anything. One written by hand while resolving an update conflict still counts, since it lands in this project's own source
  • the ruff ignore list signal is likewise off during an update, where a new entry arrived with the template rather than being chosen here
  • conflict markers keep being reported everywhere, including in template owned files, since that is exactly the "the update could not be merged" case worth hearing about

[9.2.0] 2026-08-23

Changed

• the lint rules in .claude/rules/ now say what to do when a rule cannot be satisfied
  • the ban on # noqa, on growing the ignore list and on loosening mypy left no permitted resolution for the rare rule that is wrong in context - S701 demands HTML autoescaping, which corrupts a Jinja template rendering JSON, so obeying it writes the bug it exists to prevent
  • the permitted resolution, once a human has agreed, is a # noqa carrying its reason - never a new ignore entry, which would silence the rule for unexamined code as well
• plugin: the plugin-implementation skill says what a plugin icon has to look like, not only where to put it
  • no colour of its own (currentColor on the root svg) so the mark follows the workspace theme, and a transparent background so it does not sit as a coloured tile among icons that are
  • nothing in task check or plugin discovery complains about either, so both were previously found only by looking at the running workspace
• plugin: the plugin-implementation skill warns that a union type annotation on a parameter breaks discovery
  • without an explicit param_type, the type is derived from the annotation, and a union raises TypeError: issubclass() arg 1 must be a class at import time - which removes every plugin in the package from the workspace while task check stays green
• plugin: the plugin-implementation skill records that DataIntegration clears a dependent parameter when one of its dependencies changes
  • the clearing propagates along a chain, so a chained parameter never holds a value from an earlier selection - there is no stale combination to defend against, and such a parameter can safely be mandatory

Fixed

• the session end check no longer reports the copier update that installs it
  • .claude/hooks/template-feedback.py counted any changed template owned file as a finding, and an update changes all of them - so taking a new template version made the check accuse you of the act of taking it
  • when the working tree carries a changed _commit in .copier-answers.yml, those paths are the update and no longer count; an added # noqa, a grown ruff ignore list and leftover conflict markers still do, since those are real findings even mid-update

[9.1.0] 2026-08-23

Added

• generated projects can report findings back to the template
  • a template-feedback skill checks what the template has already decided, drafts a GitHub issue and files it on eccenca/cmem-plugin-template - always after showing you the exact text, never on its own
  • it never names your repository and never pastes code from it, since the template tracker is public while most generated projects are not: an issue carries the template version, project_type and whether github_page/pypi are answered
  • gh issue create is deliberately not in the pre-approved commands, so filing always asks for permission; the read-only gh issue list and gh search issues are pre-approved
  • a new Stop hook, .claude/hooks/template-feedback.py, run through the new task template:feedback-check, reminds the agent at the end of a session - but only when this working tree shows that something in the template got in the way: a template owned file was edited, a # noqa or # type: ignore was added, a rule joined the ruff ignore list, or a copier update left conflicts behind
    • this hook can hold a session open for one extra turn when it finds such evidence, so that the agent can decide whether the finding is worth reporting. Answering "this is specific to this project" ends the session, and it asks at most once per session
    • create an empty .claude/no-template-feedback file to switch it off - that file belongs to your project, so copier update will not take it away

[9.0.1] 2026-08-22

Fixed

• the template's own dependabot configuration, which 9.0.0 broke
  • the jinja directory name it pointed at reads as a glob to dependabot, which rejected the whole file - so no dependency updates were opened at all, not even for the template's own CI
  • the condition moved to _exclude in copier.yml, so the generated workflows keep a literal path
  • nothing changes for generated projects: updating to 9.0.1 renders exactly the same files as 9.0.0

[9.0.0] 2026-08-22

Added

• generated projects ship a .claude/ directory with agent support for Claude Code
  • .claude/rules/ is read in every session: which files belong to the template, that lint findings are fixed instead of silenced, and that user-visible changes need a changelog entry
  • .claude/settings.json allows the everyday commands (task check, task format:fix, task build, pytest, ruff, mypy) without a prompt, while task install and task uninstall still have to be confirmed
  • it also formats edited files by running task format:fix after each agent edit - remove the hooks block from .claude/settings.json if you do not want that
  • a copier-update skill describes how to take a new template version, and a release skill how to cut a release - the latter only in github hosted projects, see below
  • plugin projects additionally receive the plugin-documentation, plugin-testing and plugin-implementation skills, plus a rules file about cmem-plugin-base, the needs_cmem marker and the tasks that change a running deployment
  • the plugin-implementation skill records the conventions the plugin fleet converged on: reaching a deployment with cmem-client (and that cmem.cmempy.* is deprecated), logging through self.log, Icon(package=__package__), explicit port declarations, honouring workflow cancellation, reporting progress from inside the entity loop, typing secrets as Password, and writing custom parameter types - including that autocompletion_depends_on_parameters hands its values to autocomplete() positionally
• no CLAUDE.md is written into generated projects
  • that file belongs to your project, is never touched by copier update, and is read alongside the shipped rules

Changed

• a project is now generated with the pipeline it actually uses, not with both
  • github_page decides the host: with a URL you get .github/workflows/ and no .gitlab-ci.yml, left blank you get .gitlab-ci.yml and no .github directory
  • pypi decides the publish path: the github publish.yml, or the manual pypi job of the gitlab pipeline, are only generated when it is answered yes
  • check both answers before updating, because copier update removes the files they no longer select
  • both questions used to be documented as badge and link decoration, so a stale answer is likely: their help texts now say what they generate
  • if you are built on gitlab but keep a github page, clear github_page - a mirror is not a build host, and the badges are not worth the pipeline
  • the release skill follows the same answers: it is delivered for github hosted projects only, and describes the tag triggered publish only when pypi is set
• the Corporate Memory badge is now served from the production documentation instead of dev.documentation.eccenca.com
  • the badge itself is unchanged - the development host served the same JSON, but is not a deployment anybody promises to keep up

[8.8.0] 2026-08-21

Changed

• github: refresh the Trivy DB cache in the generated check workflow
  • the key was constant, so the database was saved once and never replaced
  • it now rotates per run with a prefix fallback, as the template's own CI does
• copier >= v9 is now enforced by the template, not only documented
  • an older copier fails with a clear message instead of an obscure error
  • v9 is a support policy: it is the only major this template is tested against

Removed

• the empty [tool.pytest.ini_options] addopts setting, which configured nothing

Fixed

• .gitignore no longer ignores every *.xml and *.html file in the project
  • they were meant for the reports in dist/, which is already ignored anyway
  • a plugin shipping an XML resource or an HTML page had it silently untracked
  • after copier update, such files may newly appear as untracked
• .gitignore no longer ignores version.py, unused since poetry-dynamic-versioning

[8.7.0] 2026-08-20

Changed

• github: update actions/cache to v6 in the generated check workflow
  • v5 moved to the node24 runtime and needs an Actions Runner >= 2.327.1
  • only relevant for projects building on self-hosted runners

[8.6.0] 2026-08-20

Changed

• use cmem-plugin-base v4.20.0 (Corporate Memory 26.2)
• plugin: example test code now uses cmem-client instead of cmem-cmempy
• github: update actions in generated workflows
  • checkout v7, setup-task v3, setup-python v7, action-junit-report v6
• ruff: asserts (S101) are now allowed in tests/ only
  • previously allowed everywhere; assert in plugin code is now reported
• ruff: unused args (ARG) are now allowed in tests/
• ruff: ignore CPY001 (missing copyright notice)
• update dependencies esp. trivy (0.73.0.1) and ruff (0.16.2)

Fixed

• generated Taskfile: custom tasks file is TaskfileCustom.yaml
  • the file header wrongly named it TaskfileCustom.yml, which is silently ignored
• generated Taskfile: typo in the file header
• plugin: typo in the uninstall task description
• README: poetry requirement is >= v2.1 ([tool.poetry.requires-plugins] needs poetry 2.x)
• README: task list was outdated
• README: drop manual poetry self add step (required plugins are installed automatically)
• gitlab: remove misleading comment on the pypi job (it is manual, not tag-restricted)
• trivyignore: drop stale CVE-2022-39280 suppression from the safety era, explain the file instead

[8.5.0] 2026-06-24

Changed

• gitlab: use python image v3.13.13
• trivy: use 0.71.2.1
• poetry: use explicit plugin requirements instead of Taskfile checks

[8.4.1] 2026-04-14

Fixed

• ruff UP043 issue in example plugin code

[8.4.0] 2026-04-14

Added

• export requirements.txt on build

Changed

• gitlab: use python image v3.13.12
• use cmem-plugin-base v4.16.1 (Corporate Memory 26.1)

Fixed

• ruff target-version now py313
• gitignore: .claude/settings.local.json

[8.3.2] 2026-03-02

Changed

• update trivy-py-ecc to v0.69

[8.3.1] 2026-02-04

Fixed

• update dependencies, no vulnerabilities

[8.3.0] 2026-01-21

Changed

• all: update dev-dependencies

[8.2.1] 2025-12-10

Fixed

• git repository init check (is now able to work inside submodule)

[8.2.0] 2025-11-27

Fixed

• trivy scan now includes dependencies
• github, gitlab: disable vex notification
• github, gitlab: disable progress

Added

• github, gitlab: trivydb cached between runs

[8.1.0] 2025-11-27

Changed

• replace trivy-py with trivy-py-ecc ^0.67.2

[8.0.0] 2025-11-24

Changed

• all: switch to python 3.13.8
• all: update dev-dependencies
• use trivy as vulnerability scanner in exchange for safety
• pre-commit: use python 3.13

[7.3.0] 2025-07-04

Changed

• upgrade base dependency to 4.12.1
• all: update dev-dependencies

Fixed

• lower cmemc dependency restriction in order to avoid dependency deadlock
• gitlab pipeline - pytest job: export all paths in dist as artefacts

[7.2.0] 2025-05-28

Added

• deptry check step

Changed

• all: update dev-dependencies
• cmem-plugin-base -> 4.10.2 (Corporate Memory 25.1.x)
• update cmemc dev-dependency to v25
• plugin: example test code now uses integrated Context classes
• all: make poetry:install task non-internal (to allow calls from custom tasks)

[7.1.0] 2025-02-10

Changed

• all: update dev-dependencies
• plugin: tailored for Corporate Memory v24.3.x

[7.0.0] 2024-09-09

Changed

• Generalization of the template
  • You can create now projects of the following types:
    • eccenca Corporate Memory plugins (same as before)
    • Generic Python Projects (this is new)
  • The first template question will ask you for the project type.
  • Most features depend on this project type and will adapt to the decision.

Added

• more shields

Fixed

• limitations of the 6.x template version regarding project name

[6.4.0] 2024-08-18

Changed

• dependency updates (ruff 0.5, pytest 8, pytest-cov 5)
• cmem-plugin-base -> 4.7.0 (Corporate Memory 24.2.x)
• github: update to actions/setup-python@v5
• github: update to arduino/setup-task@v2

[6.3.1] 2024-06-03

Security

• ignore dev dependency security issue 70612 for jinja2

[6.3.0] 2024-05-22

Changed

• update ruff

Fixed

• exampe test

[6.2.0] 2024-05-06

Added

• pytest-html report generation

Changed

• coverage report does some advanced exclusion:
  • https://coverage.readthedocs.io/en/7.5.0/excluding.html#advanced-exclusion
• update dependencies, esp. ruff

Security

• ignore pips 67599 safety issue

[6.1.0] 2024-02-02

Fixed

• check:ruff now creates always a junit XML file
• ignore FIX002 - allow to add TODO notes in the code

Changed

• ignore FBT (boolean trap)

[6.0.1] 2023-11-16

Fixed

• pre-commit hook switched to ruff as well

[6.0.0] 2023-11-16

Changed

• integrate ruff (removing bandit, flake8, black and pylint)
• use plugin base 4.3.0 (cmem-cmempy >= 23.3)
• use poetry-dynamic-versioning option bump=true
  • 0.0.1.devX.. instead of 0.0.0.postX

Fixed

• race condition in deploy task (#19)
• missing check for poetry versioning plugin on build task

[5.3.4] 2023-11-06

Fixed

• avoid safety issue 62044 for pip less than 23.3

[5.3.3] 2023-10-13

Fixed

• pylint/pillow dependencies to avoid errors

[5.3.2] 2023-10-13 (yanked)

Fixed

• pylint/pillow dependencies to avoid errors

[5.3.1] 2023-09-14

Fixed

• gitlab CI: artifact path for pytet

[5.3.0] 2023-09-08

Changed

• forward mikepenz/action-junit-report to v4

[5.2.0] 2023-09-08

Fixed

• github pipeline: use concurrency to avoid integration test issues

Changes

• update checkout action to v4
• extend documentation
• clean up local build plan / task documentation

[5.1.0] 2023-09-05

Changed

• use cmem-plugin-base 4.1.0 which is used by Corporate Memory 23.2

Added

• .python-version to the project root in order to control pyenv
  • see https://realpython.com/intro-to-pyenv/ for a tutorial

Fixed

• Windows / MinGW compatibility
• used github actions
• build plan
• Unneeded safety ignores

[5.0.2] 2023-07-10

Fixed

• github pipeline: remove cache config (poetry not found)

[5.0.1] 2023-07-07

Fixed

• README: pypi links

[5.0.0] 2023-07-06

Changed

• switch to (and enforce) python 3.11
• switch to cmem-plugin-base 4.x (which is the base for Corporate Memory 23.2)

[4.2.0] 2023-05-11

Added

• check for correct poetry-dynamic-versioning plugin
• check for valid pyproject.toml (poetry check)

[4.1.0] 2023-04-28

Changed

• forward to cmem-plugin-base 3.1.0 (23.1 release)
• forward dev dependencies

[4.0.0] 2023-03-13

Changed

• upgrade dependencies incl. cmem-plugin-base to 3.0.0
  • This includes backwards incompatible changes.
  • Migration Notes: https://github.com/eccenca/cmem-plugin-base/blob/main/CHANGELOG.md

[3.6.2] 2023-03-10

Changed

• update github actions checkout, cache and and setup-python (deprecated)

[3.6.2] 2023-03-10

Changed

• update github actions checkout, cache and and setup-python (deprecated)

[3.6.1] 2023-02-17

Changed

• change development dependencies to group notation.

[3.6.0] 2023-02-13

Changed

• updates of black, mypy and coverage

Fixed

• gitlab ci yml migrated to gitlab >15 compatibility

[3.5.1] 2023-01-18

Added

• github_page question (to add icons and homepage links)
• pypi question (to add icons and links)
• made for badge in README

Fixed

• add github token for task checkout step in the github workflow to avoid quota errors

[3.4.1] 2022-11-24

Added

• dependabot github action on daily basis
• mypy and flake8 execution for tests code

Changed

• github actions to latest versions

[3.4.0] 2022-10-21

Added

• pytest memray memory profiler plugin
• enable .env file usage
• Taskfile with clean and check tasks to test the template
• github build plan to test the template

Changed

• upgrade pytest-cov to 4.x
• upgrade mypy to 0.982

Removed

• unneeded poetry:init task

[3.3.2] 2022-09-14

Fixed

• github: remove unneeded secrets
• github: use secrets envs only in pylint step

[3.3.1] 2022-09-14

Fixed

• github: publish workflow now only executed on tags

[3.3.0] 2022-09-14

Changed

• package versions are now generated with the poetry dynamic versioning plugin

Added

• github: publication of tagged versions to pypi.org (if PYPI_TOKEN is set)
• gitlab: publication of tagged versions to pypi.org (if PYPI_TOKEN is set)

[3.2.0] 2022-09-14

Changed

• gitlab: split check phase into separate jobs
• github: split check phase into separate jobs

Added

• gitlab: manual publish:pypi job which uses PYPI_TOKEN

[3.1.2] 2022-09-07

Changed

• gitlab build plan: forward base image to v3.9.12-1

[3.1.1] 2022-09-01

Fixed

• public README

[3.1.0] 2022-09-01

Added

• .gitattributes to reclassify *.py.jinja files as python
• action trigger on main branch
• set CMEM_BASE_URI and OAUTH_CLIENT_SECRET from github secrets
• needs_cmem annotation to run test only of cmem environment is available
• Dummy contexts in utils that can be used in tests
• lifetime transform plugin
• option to extend tasks with TaskfileCustom.yml

Changed

• use plugin base ^2.1.0

[3.0.1] 2022-07-12

Fixed

• execution test now gives empty context

[3.0.0] 2022-07-12

Changed

• use plugin base ^2
• change interface of execute

Removed

• all copier after task (they often break the execution)

[2.1.2] 2022-06-13

Added

• github action to run task check

Fixed

• remove useless option values not needed by latest pylint

[2.1.0] 2022-06-10

Changed

• ignore safety for librdf dependency

[2.0.0] 2022-05-27

Changed

• migration to copier 6

[1.0.0] 2022-05-09

Added

• initial version for copier 5