chore(deps): bump piccolo from 0.119.0 to 1.1.1 in /backend

[dependabot]

Bumps piccolo from 0.119.0 to 1.1.1.

Release notes

Sourced from piccolo's releases.

1.1.1

Piccolo allows the user to specify savepoint names which are used in transactions. For example:

async with DB.transaction() as transaction:
    await Band.insert(Band(name='Pythonistas'))
# Passing in a savepoint name is optional:
savepoint_1 = await transaction.savepoint('savepoint_1')
await Band.insert(Band(name='Terrible band'))
Oops, I made a mistake!
await savepoint_1.rollback_to()

Postgres doesn't allow us to parameterise savepoint names, which means there's a small chance of SQL injection, if for some reason the savepoint names were generated from end-user input. Even though the likelihood is very low, it's best to be safe. We now validate the savepoint name, to make sure it can only contain certain safe characters. Thanks to @​Skelmis for making this change.

1.1.0

Added support for Python 3.12.

Modified create_pydantic_model, so additional information is returned in the JSON schema to distinguish between Timestamp and Timestamptz columns. This will be used for future Piccolo Admin enhancements.

1.0.0

Piccolo v1 is now available!

We migrated to Pydantic v2, and also migrated Piccolo Admin to Vue 3, which puts the project in a good place moving forward.

We don't anticipate any major issues for people who are upgrading. If you encounter any bugs let us know.

Make sure you have v1 of Piccolo, Piccolo API, and Piccolo Admin.

1.0a3

Namespaced all custom values we add to Pydantic's JSON schema for easier maintenance.

1.0a2

All of the changes from 0.120.0 merged into the v1 branch.

1.0a1

Initial alpha release of Piccolo v1, with Pydantic v2 support (thanks to @​sinisaos for helping with this).

0.121.0

Modified the BaseUser.login logic so all code paths take the same time. Thanks to @​Skelmis for this.

0.120.0

Highlights

Improved how ModelBuilder generates JSON data.

The number of password hash iterations used in BaseUser has been increased to keep pace with the latest guidance from OWASP - thanks to @​Skelmis for this.

... (truncated)

Changelog

Sourced from piccolo's changelog.

1.1.1

Piccolo allows the user to specify savepoint names which are used in transactions. For example:

.. code-block:: python

async with DB.transaction() as transaction:
    await Band.insert(Band(name='Pythonistas'))
# Passing in a savepoint name is optional:
savepoint_1 = await transaction.savepoint('savepoint_1')
await Band.insert(Band(name='Terrible band'))
Oops, I made a mistake!
await savepoint_1.rollback_to()

Postgres doesn't allow us to parameterise savepoint names, which means there's a small chance of SQL injection, if for some reason the savepoint names were generated from end-user input. Even though the likelihood is very low, it's best to be safe. We now validate the savepoint name, to make sure it can only contain certain safe characters. Thanks to @​Skelmis for making this change.

---

1.1.0

Added support for Python 3.12.

Modified create_pydantic_model, so additional information is returned in the JSON schema to distinguish between Timestamp and Timestamptz columns. This will be used for future Piccolo Admin enhancements.

---

1.0.0

Piccolo v1 is now available!

We migrated to Pydantic v2, and also migrated Piccolo Admin to Vue 3, which puts the project in a good place moving forward.

We don't anticipate any major issues for people who are upgrading. If you encounter any bugs let us know.

Make sure you have v1 of Piccolo, Piccolo API, and Piccolo Admin.

... (truncated)

Commits

• bbd2e4a bumped version
• 82679eb Merge pull request from GHSA-xq59-7jf3-rjc6
• e4946d8 add docs about avoiding type warnings for pydantic models which are variables...
• bfb6acd upgrade slotscheck (#901)
• d4cf588 bumped version
• 6cb005b add Python 3.12 support (#888)
• febe5bb JSON schema - indicate that a column is timestamptz (#897)
• 28fe3a4 bumped version
• 9e5fae9 v1 (#893)
• d1f6c35 Support Postgres 16 (#886)
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
munro	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 5, 2023 10:28pm