[v3.0.0] Feat!: new colors, parser and presenter splited and path command

Release v3.0.0

June 19, 2026

This release brings major CLI improvements, a cleaner architecture, and several breaking changes aimed at making doggy-notes more consistent and easier to maintain.

⚠️ Breaking Changes

• "add" has been renamed to "create".
• "delete" and "read" now use "tag" and "id" subcommands instead of flags.
• "--asc" and "--desc" have been replaced by the new "--order" option.

Added

• New "path" command to display doggy-notes files as a tree.
• New console theme colors.
• Centralized "help_messages" module for easier maintenance.
• Previous versions are now documented in the changelog.

Changed

• Help messages are now shorter and simpler.
• All commands now use the doggy-notes console for consistent output.
• Validation logic has been moved to use cases, improving separation of concerns.
• Logging now uses ".log" files.
• Internal architecture has been reorganized with better separation of responsibilities.

Fixed

• Improved output readability with status glyphs ("✓" and "✗").
• Reduced complexity by splitting large functions into smaller units.
• Added log management to prevent excessive log growth.

---

For more details, see the CHANGELOG.md.

[v2.2.0] Feat: tags table created and note_errors refactored

Release v2.2.0

May 30, 2026

Changed

• Before this update tags were searched in notes, using commas in the start and in the end of the tags. Now tags have a table, making searchs faster, more secure and more professional
• note_errors has errors with more transparenty names and is more organized

Fixed

• migrations.py refactored to work in the new structure

---

For more details, see the CHANGELOG.md.

[v2.1.2] Fix: Cli commands imports centralized in dependencies.py and schema_version created

Release v2.1.2

May 24, 2026

Changed

• Now cli commands imports are centralized in dependencies.py

Fixed

• schema_version created to resolve future problems, like changing the note structure don't be a problem to previously created notes, them update automatically
• Bugs solved in delete and list functions

---

For more details, see the CHANGELOG.md.

[v2.1.1] Fix: Timezone problem solved and working assets

Release v2.1.1

May 22, 2026

Fixed:

• In v2.1.0 date was showed based in utc time zone. Now it's showed based in local time zone
• Now doggy-notes can be installed via git hub assets

---

For more details, see the CHANGELOG.md.

[v2.1.0] Feat: Edit and read functions added

Release v2.1.0

May 20, 2026

This release introduces major improvements to the codebase architecture and user experience. We've added essential CRUD operations, improved help documentation, and implemented a more robust storage system with migrations.

Added

• Edit & Read Functions - New operations to modify and retrieve notes with improved workflows
• Command Usage Examples - Comprehensive examples in help messages for better user guidance
• CHANGELOG.md - Added to improve project organization and documentation
• NoteParser - New utility for centralized note parsing logic
• query_result Module - Centralizes the get function in services for better data handling
• Migrations System - Ensures secure and reliable storage initialization without errors
• note_errors Module - Custom error handling for improved error messages and user experience
• Centralized Paths - All project paths are now managed in a single configuration

Changed

• Universal Note Model - Commands now use a standardized model for note data, making it easier to integrate future APIs and expand functionality
• Help Messages - Completely redesigned with detailed descriptions, output models, and practical examples
• NotePresenter - Improved responsibility control for better separation of concerns

Fixed

• Storage Initialization - Resolved potential issues with storage setup using migrations
• Documentation - Updated README to reflect v2.1.0
• Help Documentation - Updated command help text for consistency with new version

Removed

• Unused Storage File - Cleaned up unnecessary storage configuration
• Unused Imports - Removed dead code dependencies

---

For more details, see the CHANGELOG.md.

[v2.0.1] Fix: Missing files problem solved

Missing files problem solved and minor UX improvements

• Added init.py file in all the necessary folders
• List function added in console
• Minor UX improvements to create a more solid and scalable console

[v2.0.0] Refactor: Migrate from JSON to sqlite - Broken for missing files problem

A Major UX Update + Migration from JSON to SQLite

What changed in the UX?

• Rich was added, making the output more personalized and visually appealing
• Improved error handling: each error now has its own specific message instead of a generic one
• A custom console system was created to replace direct print calls. Instead of printing raw messages, the console formats them and applies Rich styling automatically. A dedicated console system makes the project more scalable and easier to maintain

New message types

• Error messages
• Success messages
• Note messages (currently identical to list messages)

What changed in data management?

• Notes are now stored in a SQLite database
• Same note structure, improved internal architecture

Why migrate to SQLite if JSON was already enough?

This is a fair question.

I could continue using JSON without immediate problems. JSON is flexible and easy to work with, but it becomes inefficient as the project grows. Instead of handling lightweight database operations, the application needs to process entire note structures manually.

As the project scales, users may eventually store hundreds or even thousands of notes, especially with future API integrations, power users, or business usage.

In summary:

• The project is currently small, not because I want it to stay small, but because it is still growing
• The more scalable and maintainable the architecture becomes now, the easier future development will be
• JSON is simple and effective, but SQLite provides better scalability and structure
• SQLite is more complex, but with good organization it enables far more possibilities for the project

Is this version incompatible with previous releases?

Partially.

The index argument was temporarily removed from the delete function to simplify the new architecture and improve consistency. However, since backward compatibility is important, support for indexes will return in a future update.

Same functionality, better implementation.

Planned for the next version

• Add warning and list message types
• Add border styles to success messages
• Remove or refactor unused files to clean up the codebase
• Improve documentation overall

Why is this version v2.0.0 if the user experience barely changed?

Because the entire storage architecture of the application changed.

Even though the user experience remains mostly the same, the internal system was significantly redesigned. This is a major structural update and justifies a new major version.

[v1.1.1] Chore: README.md was updated and pip availability

What's new:

README.md updated

• Previously displayed code that contained errors and was out of date
• Now shows examples that work

Pip availability

• Another installation method
• Available to more people
• Simpler installation

Automatic version

• Automatic version in toml file to prevent human errors

[v1.1.0] Refactor: Argparse replaced by Typer

Argparse has been replaced by Typer. Why?

• Typer offers a more intuitive and user-friendly experience
• Typer is easily scalable
• It doesn’t require endless loops and else/if statements like Argparse does
• Among other things

What else has been added and changed?

• A commands folder has been created to store all project commands and make it scalable
• Users can now access the commands doggy --version and doggy info to view information about the installed version
• Command descriptions have been added
• Other minor improvements

[1.0.0] Docs: Finally doggy-notes releases github

What's new:

• Readme.md file teaching users how to use it
• License apatche 2.0
• Github release
• A more user-friendly CLI

Why is that the first stable version, not 0.9.0 version:

• Minor bugs fixes
• This version has a Readme.md file, version 0.9.0 not
• Before my_notes, now we have identify: doggy-notes
• And more