The Poetry configuration is invalid: - Additional properties are not allowed ('group' was unexpected)

when I deployed Django project on render
I encountered failed: above subject

my current local poetry version is 1.2.2

I following docs: Getting Started with Django on Render

my <render.yaml> file:

  • name: mysite
    databaseName: mysite
    user: mysite
    region: singapore


  • type: web
    name: mysite
    env: python
    region: singapore
    buildCommand: “./”
    startCommand: “gunicorn mysite.wsgi:application”
    • key: DATABASE_URL
      name: mysite
      property: connectionString
    • key: SECRET_KEY
      generateValue: true
      value: 4

my <> file:
#!/usr/bin/env bash

exit on error

set -o errexit

poetry install

python collectstatic --no-input
python migrate

my <pyproject.toml> file:
name = “mysite”
version = “0.1.0”
description = “”
authors = “”
readme = “”

python = “^3.9”
django = “4.0”
dj-database-url = “^1.0.0”
psycopg2-binary = “^2.9.5”
whitenoise = {extras = [“brotli”], version = “^6.2.0”}
gunicorn = “^20.1.0”


black = {version = “^22.10.0”, allow-prereleases = true}


requires = [“poetry-core”]
build-backend = “poetry.core.masonry.api”

what should I do?

The Poetry version provided by Render is < 1.2 (1.1.4 as of today). Which is problematic for anyone who has some recent Poetry config (like me).

A suggestion is to move to a deploy using Docker (not so happy of having to change all this just because of an old version of Poetry).

Another way to resolve this issue is to use the older format for dev dependencies as described in the Poetry docs.

Specifically, change [] to [].

Note that the poetry.lock file won’t be compatible between poetry versions so you’d need to remove that from your VCS as well.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.