Add maintenance plan

[bregydoc]

This pull request adds a PLAN_DE_MANTENIMIENTO.md file with a maintenance plan for pigment.

The plan outlines steps to bring the package up to date with modern Flutter and Dart, including:

• Updating SDK constraints and dependencies to support null safety and the latest stable versions.
• Refactoring the codebase to remove deprecated APIs and follow modern Dart/Flutter best practices.
• Setting up GitHub Actions workflows for tests, static analysis and formatting on each pull request.
• Adding comprehensive unit tests for color parsing and manipulation features.
• Enhancing documentation and providing examples, including a sample Flutter app.
• Reviewing and triaging issues and pull requests from the community.
• Adopting semantic versioning and maintaining a changelog for each release.

Summary by CodeRabbit

• Documentation
  • Introduced a maintenance plan document outlining ongoing tasks, including support for latest Flutter/Dart versions, code modernization, CI/CD automation, improved test coverage, enhanced documentation, active issue management, and adoption of semantic versioning.

[coderabbitai]

Walkthrough

A new maintenance plan document has been added for the pigment package. The document details tasks such as updating dependencies, refactoring code, automating CI/CD, increasing test coverage, improving documentation, managing community contributions, and adopting semantic versioning.

Changes

File(s)	Change Summary
PLAN_DE_MANTENIMIENTO.md	Added a comprehensive maintenance plan outlining ongoing and future tasks.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A plan for pigment, crisp and neat,
With tasks and goals—no small feat!
CI/CD hops in line,
Docs and tests will brightly shine.
A bunny's joy, to see it clear—
Maintained with care, all through the year! 🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch maintenance-plan-pigment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (3)

PLAN_DE_MANTENIMIENTO.md (3)

3-9: Add measurable targets, owners, and timelines
The bullets list what to do but not when, who, or the definition of done. Consider adding (a) target dates / release milestones, (b) the person or team responsible, and (c) explicit success criteria (e.g., “≥ 90 % line coverage”, “CI runs < 5 min”). This will turn the plan into an actionable roadmap.

---

3-3: Be explicit about SDK constraint changes
Mention updating pubspec.yaml’s environment: section and each dependency version so readers know exactly where to apply the change.

---

9-9: Use conventional uppercase “CHANGELOG”
Most Dart/Flutter packages use the filename CHANGELOG.md. Changing “changelog” → “CHANGELOG” aligns with community conventions.

-* **Versioning and releases:** Adopt semantic versioning, create release tags and maintain a changelog summarizing changes for each release.
+* **Versioning and releases:** Adopt semantic versioning, create release tags and maintain a **CHANGELOG** summarizing changes for each release.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2e26572 and 7cc7727.

📒 Files selected for processing (1)

• PLAN_DE_MANTENIMIENTO.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

PLAN_DE_MANTENIMIENTO.md

[grammar] ~9-~9: Ensure spelling is correct
Context: ...ing, create release tags and maintain a changelog summarizing changes for each release.

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)