-
26.16.0
StableAll checks were successful/ publish (push) Successful in 4s/ pre-check (push) Successful in 1m12s/ lint (push) Successful in 2m3s/ prettier (push) Successful in 2m33s/ unit-testing (push) Successful in 2m47s/ tsc (push) Successful in 3m1s/ sonar (push) Successful in 1m25sreleased this
2026-04-16 13:12:26 +00:00 | 0 commits to master since this release⚠️ Breaking Changes
Firebase Logger — Modular API Migration (#62)
The
createFirebaseLoggerfunction signature has changed to use the modular API
required by React Native Firebase v22+, eliminating deprecation warnings that
polluted application logs.Before:
createFirebaseLogger(analytics) // internally: analytics.logEvent(event, params)After:
import { logEvent } from '@react-native-firebase/analytics'; createFirebaseLogger(analytics, logEvent) // internally: logEvent(analytics, event, params)Update your initialization code and refer to the updated README for the full
migration example.
🔧 CI/CD Improvements
PR Quality Pipeline (#52)
Added a Forgejo Actions CI workflow (
.forgejo/workflows/pr.yaml) that runs
automatically on every pull request targetingmaster. The pipeline enforces
code quality gates in parallel: Prettier formatting, TypeScript type-checking,
ESLint linting, and Jest unit tests. SonarQube PR analysis runs after the
unit-testing job to consume the coverage artifact.Fork CI — Optional Sonar Analysis (#56)
All four workflows (
pr.yaml,dev.yaml,master.yaml,tag.yaml) now skip
the Sonar job gracefully when the required secrets/variables (SONAR_TOKEN,
SONAR_HOST_URL,SONAR_PROJECT_KEY,SONAR_PROJECT_NAME) are not configured.
Thepublishjob intag.yamlis updated to proceed when Sonar either succeeds
or is skipped, so fork-based releases are not blocked.Sonar-specific configuration has been moved out of
sonar-project.properties
and into CI variables/secrets.Fork CI —
pull_request_targetEvent (#59)The PR workflow trigger is switched from
pull_requesttopull_request_target
so the full pipeline (including Sonar) runs for fork PRs. All
actions/checkout@v4steps are pinned to the PR head SHA via
ref: ${{ github.event.pull_request.head.sha }}to avoid running code from an
ambiguous merge commit.PR Title & Commit Title Validation
- PR title format (
#<issue-number> - <description>) is now validated by CI
before other quality checks run - Commit title validation has been added to all relevant workflows with explicit
job ordering
📖 Documentation
Contributing Guidelines
CONTRIBUTING.mdhas been expanded to document commit message conventions, PR
title format, branch naming, and the CI/Sonar configuration required for fork
contributors.Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
- PR title format (