Labels

• area: build

  Relates to the Maven build process.
• area: client

  Relates to the client-side TypeScript/JavaScript code.
• area: component

  Relates to the webforj-addons-components module generally.
• area: documentation

  Related to issues/changes to documentation, such as updating or adding.
• area: service

  Relates to the webforj-addons-services module generally.
• area: testing

  General testing infrastructure or cross-cutting test concerns.
• dependencies

  Pull requests that update a dependency file
• github_actions

  Pull requests that update GitHub Actions code
• java

  Pull requests that update Java code
• javascript

  Pull requests that update Javascript code
• priority: critical

  Must be fixed immediately (e.g., production outage, security flaw).
• priority: high

  Important issue impacting core functionality or a significant number of users.
• priority: low

  Nice-to-have, minor issue, or low impact. Address when time permits.
• priority: medium

  Standard priority. Important but doesn't block core workflows or major releases.
• skip-changelog

  Ignores the PR for the release notes.
• status: blocked

  Shows that the issue or pull request is currently blocked by another issue or dependency.
• status: confirmed

  The issue has been reviewed and confirmed as valid by the maintainers.
• status: needs info

  More information is required from the reporter to proceed.
• status: needs triage

  Issue requires review by maintainers to validate and categorize.
• status: on hold

  Indicates that work on the issue or pull request has been paused and will be resumed later.
• status: progress

  Indicates that the issue or pull request is currently being worked on.
• status: ready for review

  Signals that the pull request is complete and ready for review by other team members.
• type: breaking

  Indicated backward-incompatible changes. This is crucial for release notes.
• type: bug

  Indicates that an issue is a bug or a problem that needs to be fixed.
• type: chore

  For maintenance, build, CI/CD, and bump tasks that aren't features/fixes, etc.
• type: dependencies

  Pull requests that update a dependency file
• type: documentation

  Reserved for issues related to documentation, such as updating, adding, or clarifying documentation
• type: enhancement

  Signals that the issue involves improving existing functionality.
• type: feature request

  Denotes that the issue is a request for a new feature or enhancement.
• type: fix

  Indicates a fix to a bug or a problem.