metadata.swiss

Monorepo for the opendata.swiss metadata infrastructure, including the portal frontend application and custom Piveau Consus modules.

The repository is organized as an npm workspace managing both JavaScript/TypeScript applications and Java/Maven modules:

Additional components in the repository:

• opendata.swiss/metadata: Metadata catalogues, pipelines, system tests, and harvester scripts.
• opendata.swiss/archimate: Architecture models and documentation.

This monorepo uses Changesets (@changesets/cli) to manage semantic versioning, changelogs, and release tracking across all projects.

Changesets natively operates on npm workspaces configured in the root package.json:

{
  "workspaces": [
    "opendata.swiss/ui",
    "opendata.swiss/piveau_modules/*"
  ]
}

• UI Application (opendata.swiss/ui): Uses standard package.json metadata for the Nuxt/Vue frontend.
• Piveau Maven Modules (opendata.swiss/piveau_modules/*): Each Java module contains both a Maven pom.xml and a minimal package.json defining "name" and "version". This lightweight bridge allows @changesets/cli and GitHub Actions to treat Java/Maven projects as standard workspace packages, enabling unified changelog tracking and version management.

Changesets settings are defined in .changeset/config.json:

• baseBranch: main
• changelog: Uses @changesets/changelog-github linked to opendata-swiss/metadata.swiss.
• commit: Enabled for automated version commit generation.

When submitting a pull request that modifies one or more projects, add a changeset entry:

npx changeset

1. Select the packages changed (e.g., piveau-opendata-swiss, piveau-consus-filter).
2. Choose the SemVer bump type for each selected package:
   • patch: Bug fixes, minor adjustments, dependencies.
   • minor: New features or backward-compatible additions.
   • major: Breaking changes.
3. Provide a clear summary description of the changes.
4. Commit the newly generated file in .changeset/*.md to your branch and include it in your Pull Request.

Releases are handled automatically via GitHub Actions:

1. Push to main: When PRs with changesets are merged into main, the .github/workflows/release.yaml workflow runs changesets/action@v2.
2. Version PR: Changesets opens or updates a pull request titled "Version Packages". This PR increments versions in package.json and updates CHANGELOG.md files for affected packages.
3. Release & Tagging: When the "Version Packages" PR is merged into main, releases and git tags are created automatically.