Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions .github/workflows/ci.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
name: CI

on:
push:
branches: [master]
pull_request:
branches: [master]

jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4

- uses: actions/setup-java@v4
with:
distribution: temurin
java-version: '8'
cache: maven

- name: Build and test
run: ./mvnw -B verify

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 CI skips application compilation and tests

./mvnw -B verify reports success without compiling application sources or running tests. The pom packaging omits both phases from Maven's default lifecycle. Broken application changes can pass CI.

Learn more

Maven binds compilation and test execution to the default lifecycle only for artifact packaging such as jar. This project declares pom packaging, which represents an aggregator or parent project and has no Java compile or test bindings. The workflow therefore validates dependency resolution and the configured Spring Boot goal, but not src/main/java or any future src/test/java files.

Example: A pull request can introduce invalid syntax in TopicController.java. The new CI job still exits successfully because Maven never invokes maven-compiler-plugin for this project.

Recommended fix: Change the project packaging to jar so ./mvnw -B verify exercises the normal Java lifecycle, or run a build command that explicitly compiles and tests the application. Verify the corrected workflow fails for an intentionally uncompilable source change.

Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confirmed and already called out in the PR description: <packaging>pom</packaging> is pre-existing in pom.xml, so verify only runs the Spring Boot repackage goal. Changing the packaging to jar is a build-config change outside this PR's scope (CI workflow + SECURITY.md), so I've left it as-is and flagged it to the requester as a follow-up decision.

19 changes: 19 additions & 0 deletions SECURITY.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
# Security Policy

## Supported Versions

| Version | Supported |
| ------------------------ | ------------------ |
| `master` (0.1.0) | :white_check_mark: |
| Older releases/branches | :x: |

## Reporting a Vulnerability

Please report security vulnerabilities **privately** through GitHub Security
Advisories: open the repository's **Security** tab and click
**"Report a vulnerability"**.

**Do not open public GitHub issues for security vulnerabilities.**

We aim to acknowledge and respond to vulnerability reports within
**5 business days**.
Empty file modified mvnw
100644 → 100755
Empty file.
Loading