comment out old release workflow

Author: DrSatyr

AGENTS.md

@@ -0,0 +1,36 @@
+# Repository Guidelines
+
+## Project Structure & Modules
+- Root is a Maven multi-module project using the Maven Wrapper (`mvnw`).
+- Modules: `core` (library), `cli` (fat-jar CLI), `maven` (Maven plugin), `maven-example` (plugin usage example).
+- Tests live under `<module>/src/test/java`, with fixtures in `<module>/src/test/resources` (e.g., `core/src/test/resources`).
+
+## Build, Test, and Run
+- Build all modules: `./mvnw clean package`
+- Run tests only: `./mvnw test`
+- Format code: `./mvnw fmt:format` (runs pre-commit via githook as well)
+- CLI jar (shaded): `cli/target/openapi-diff-cli-<version>-all.jar`
+  - Example run: `java -jar cli/target/openapi-diff-cli-2.2.0-SNAPSHOT-all.jar old.yaml new.yaml --markdown diff.md`
+- Docker (optional): `docker build -t local-openapi-diff .` then run as shown in README.
+
+## Coding Style & Naming
+- Language: Java 8 (`maven.compiler.source/target=1.8`).
+- Formatter: Google Java Format via `fmt-maven-plugin` (use `./mvnw fmt:format`; do not hand-wrap).
+- Packages: `org.openapitools.openapidiff...`
+- Tests: JUnit 5; name classes `*Test.java` and use clear method names (Given_When_Then optional).
+
+## Testing Guidelines
+- Framework: JUnit Jupiter (5.x); assertions via AssertJ.
+- Run module tests: `./mvnw -pl <module> -am test`
+- Coverage: JaCoCo agent is configured; keep or improve coverage around changed code.
+- Add minimal, focused tests near the change (unit in `core`, integration/usage in `cli` or `maven`).
+
+## Commit & Pull Request Guidelines
+- Style: Conventional Commits (e.g., `feat(core): add schema diff`, `fix(cli): handle empty URLs`, `build(deps): bump junit-bom`).
+- Message: imperative, concise subject (<72 chars), details in body; reference issues (e.g., `Fixes #123`).
+- PRs: include a clear summary, scope/module, reasoning, and before/after behavior; link issues; include CLI examples or output snippets when relevant.
+- CI must pass; run `./mvnw fmt:format test package` locally before opening PR.
+
+## Security & Configuration
+- Prefer local files for specs during tests; avoid fetching remote URLs in unit tests.
+- CLI supports `--config-file` and `--config-prop` to override defaults; include sample configs in tests when adding new checks.

qodana.yaml

@@ -0,0 +1,44 @@
+#-------------------------------------------------------------------------------#
+#               Qodana analysis is configured by qodana.yaml file               #
+#             https://www.jetbrains.com/help/qodana/qodana-yaml.html            #
+#-------------------------------------------------------------------------------#
+version: "1.0"
+
+#Specify inspection profile for code analysis
+profile:
+  name: qodana.starter
+
+#Enable inspections
+#include:
+#  - name: <SomeEnabledInspectionId>
+
+#Disable inspections
+#exclude:
+#  - name: <SomeDisabledInspectionId>
+#    paths:
+#      - <path/where/not/run/inspection>
+
+projectJDK: "21" #(Applied in CI/CD pipeline)
+
+#Execute shell command before Qodana execution (Applied in CI/CD pipeline)
+#bootstrap: sh ./prepare-qodana.sh
+
+#Install IDE plugins before Qodana execution (Applied in CI/CD pipeline)
+#plugins:
+#  - id: <plugin.id> #(plugin id can be found at https://plugins.jetbrains.com)
+
+# Quality gate. Will fail the CI/CD pipeline if any condition is not met
+# severityThresholds - configures maximum thresholds for different problem severities
+# testCoverageThresholds - configures minimum code coverage on a whole project and newly added code
+# Code Coverage is available in Ultimate and Ultimate Plus plans
+#failureConditions:
+#  severityThresholds:
+#    any: 15
+#    critical: 5
+#  testCoverageThresholds:
+#    fresh: 70
+#    total: 50
+  
+#Qodana supports other languages, for example, Python, JavaScript, TypeScript, Go, C#, PHP
+#For all supported languages see https://www.jetbrains.com/help/qodana/linters.html
+linter: jetbrains/qodana-jvm-community:2025.2