Skip to content

Releases: caltechlibrary/template

Release 1.26.0

25 Jan 01:31
Compare
Choose a tag to compare

Changes in this release:

  • Addition of workflow for Baler
  • Addition of workflow & config file for YAMLlint, a YAML file linter
  • Addition of .github/SECURITY.md file, to follow GitHub best practices

Release 1.25.0

10 Jan 19:34
Compare
Choose a tag to compare

Changes:

  • Make programmingLanguage field in codemeta.json be a list.
  • Remove .github/workflows/ISSUE_TEMPLATE.md because it is not actually being used by Baler.

Release 1.24.0 – update copyright year in codemeta template file

09 Jan 16:31
Compare
Choose a tag to compare

Release 1.23.0 – minor fixes and updates

09 Jan 00:37
Compare
Choose a tag to compare
v1.23.0

fix: indentation of codemeta-TEMPLATE.json

Release 1.22 – add Markdown linter GitHub Actions workflow

13 Dec 03:13
Compare
Choose a tag to compare

This release adds a new GitHub Actions workflow to run a Markdown linter program automatically over the .md files.

This release also fixes a few lint errors in a few of the existing Markdown files.

Release 1.21.0 – update more fix and fix incomplete merge

27 Nov 20:50
Compare
Choose a tag to compare

Update more files, in the process fixing an incomplete merge that I didn't notice until I tried to do release 1.20.0.

Release 1.19.0 – update copyright year and codemeta.json template

27 Nov 20:31
Compare
Choose a tag to compare

This updates codemeta-TEMPLATE.json to the expanded version evolved during the development of IGA. It also updates the copyright year in the LICENSE file.

Add iga and update codemeta

25 May 23:32
Compare
Choose a tag to compare

This release adds the InvenioRDM GitHub Archiver and updates the codemeta file and templates to the latest version.

We don't set the 'parent' variable in iga specifically because this repository is a template.

Release 1.17 – remove LICENSE.html

29 Jul 19:44
Compare
Choose a tag to compare

Turns out the LICENSE.html file confuses GitHub's license finder. I can't remember why I thought it was useful in the first place, so let's remove it and be done with it.

Release 1.16.0 – Update approach to `.gitignore`

15 Jul 01:52
Compare
Choose a tag to compare

This release changes the default .gitignore contents and the recommended practices around it.

The new approach is to add only project-specific rules in the .gitignore. Rules that apply to a person's way of doing things (and the particular tools they happen to use) should instead go into a user's global git ignore file. For example, Emacs checkpoint and backup files are things that are not specific to a given project; rather, Emacs users will see them created everywhere, in all projects, because they're a byproduct of using Emacs, not a consequence of working on a particular project. Thus, they belong in a user's global ignores list, not in this project .gitignore.