Skip to content

Releases: mealie-recipes/mealie

v0.5.1 - Bug Fixes

17 Jun 17:04
903a9d8
Compare
Choose a tag to compare

Bug Fixes

  • Fixed #538 - Missing Ingredients on Editor
  • Fixed error on webhooks for new groups
  • Fixed various icons references

v0.5.0 too many things!

17 Jun 07:12
e2b9f02
Compare
Choose a tag to compare

v0.4.3 Hot Fixes!

20 Apr 19:59
1f35742
Compare
Choose a tag to compare

v0.4.2

17 Apr 20:58
0f5a564
Compare
Choose a tag to compare

v0.4.1 Patch

09 Apr 17:02
e11577f
Compare
Choose a tag to compare

Fixes docker startup error where the initial scripts aren't called and the database is not initialized.

Frontend/UI Improvements

08 Apr 20:35
9c379df
Compare
Choose a tag to compare

Note: v0.4.1 was removed from dockerhub. Use tag v0.4.1a for patched image.
Release Notes

v0.4.0

31 Mar 15:25
01d991f
Compare
Choose a tag to compare

v0.3.0

21 Feb 05:23
38e20ba
Compare
Choose a tag to compare

v0.3.0

Bug Fixes

  • Fixed open search on / when in input. - Closes #174
  • Error when importing recipe: KeyError: '@type' - Closes #145
  • Fixed Import Issue - bhg.com - Closes #138
  • Scraper not working with recipe containing HowToSection - Closes #73

Features and Improvements

  • Improved Nextcloud Imports
  • Improved Recipe Parser!
  • Open search with / hotkey!
  • Database and App version are now split
  • Unified and improved snackbar notifications
  • New Category/Tag endpoints to filter all recipes by Category or Tag
  • Category sidebar now has show/hide behavior on mobile
  • Settings menu on mobile is improved
  • Meal Planner
    • You can now restrict recipe categories used for random meal-plan creation in the settings menu
    • Recipe picker dialog will now display recipes when the search bar is empty
    • Minor UI improvements
    • Shopping lists! Shopping list can now be generated from a meal plan. Currently ingredients are split by recipes or there is a beta feature that attempts to sort them by similarity.
  • Recipe Viewer
    • Categories, Tags, and Notes will now be displayed below the steps on smaller screens
  • Recipe Editor
    • Text areas now auto grow to fit content
    • Description, Steps, and Notes support Markdown! This includes inline html in Markdown.
  • Imports
    • A revamped dialog has been created to provide more information on restoring backups. Exceptions on the backend are now sent to the frontend and are easily viewable to see what went wrong when you restored a backup. This functionality will be ported over to the migrations in a future release.

v0.2.1 - Hotfixes

11 Feb 04:47
c430c8d
Compare
Choose a tag to compare
  • Fixes upload image error when no photo was scrapped
  • Use "/" to open recipe search!
  • Fixes no last_recipe.json not updating
  • Added markdown rendering for notes
  • New notifications
  • Minor UI improvements
  • Recipe editor refactor
  • Settings/Theme models refactor

v0.2.0 - Now with Tests!

08 Feb 18:48
b3573dc
Compare
Choose a tag to compare

v0.2.0 - Now with Test!

This is, what I think, is a big release! Tons of new features and some great quality of life improvements with some additional features. You may find that I made promises to include some fixes/features in v0.2.0. The short of is I greatly underestimated the work needed to refactor the database to a usable state and integrate categories in a way that is useful for users. This shouldn't be taken as a sign that I'm dropping those feature requests or ignoring them. I felt it was better to push a release in the current state rather than drag on development to try and fulfill all of the promises I made.

Database Woes! I have not yet implemented a database migration service. As such, upgrades cannot be done by simply pulling the image. You must first export your recipes, update your deployment, and then import your recipes. This pattern is likely to be how upgrades take place prior to v1.0. After v1.0 migrations will be done automatically.

Bug Fixes

  • Remove ability to save recipe with no name
  • Fixed data validation error on missing parameters
  • Fixed failed database initialization at startup - Closes #98
  • Fixed misaligned text on various cards
  • Fixed bug that blocked opening links in new tabs - Closes #122
  • Fixed router link bugs - Closes #122
  • Fixed navigation on keyboard selection - Closes #139

Features and Improvements

  • 🐳 Dockerfile now 1/5 of the size!

  • 🌎 UI Language Selection + Additional Supported Language

  • Home Page

    • By default your homepage will display only the recently added recipes. You can configured sections to show on the home-screen based of categories on the settings page.
    • A new sidebar is now shown on the main page that lists all the categories in the database. Clicking on them navigates into a page that shows only recipes.
    • Basic Sort functionality has been added. More options are on the way!
  • Meal Planner

    • Improved Search (Fuzzy Search)
    • New Scheduled card support
  • Recipe Editor

    • Ingredients are now sortable via drag-and-drop
    • Known categories now show up in the dropdown - Closes 83
    • Initial code for data validation to prevent errors
  • Migrations

    • Card based redesign
    • Upload from the UI
    • Unified Chowdown / Nextcloud import process. (Removed Git as a dependency)
  • API

    • Category and Tag endpoints added
    • Major Endpoint refactor
    • Improved API documentation
    • Link to your Local API is now on your /settings/site. You can use it to explore your API.
  • Style

    • Continued work on button/style unification
    • Adding icons to buttons
    • New Color Theme Picker UI

Development

  • Fixed Vetur config file. Autocomplete in VSCode works!
  • File/Folder restructuring
  • Added Prettier config
  • Fixed incorrect layout code
  • FastAPI Route tests for major operations - WIP (shallow testing)

Breaking Changes

  • API endpoints have been refactored to adhere to a more consistent standard. This is a WIP and more changes are likely to occur.
  • Officially Dropped MongoDB Support
  • Database Breaks! We have not yet implemented a database migration service. As such, upgrades cannot be done by simply pulling the image. You must first export your recipes, update your deployment, and then import your recipes. This pattern is likely to be how upgrades take place prior to v1.0. After v1.0 migrations will be done automatically.