v5.4.1

5.4.1 (2024-04-01)

Bug Fixes

• deps: update octokit monorepo (major) (#158) (39cbf11)

v5.4.0

5.4.0 (2023-10-30)

Features

• support iteration fields (#95) (e581c3d)

v5.3.1

5.3.1 (2023-10-05)

Bug Fixes

• remove console.log debug statements (7f278d9)

v5.3.0

5.3.0 (2023-10-05)

Features

• truncate constructor option (#143) (26d7719), closes #142

v5.2.0

5.2.0 (2023-10-05)

Features

• GitHubProjectInvalidValueError (#141) (c3afa6e), closes #136

v5.1.0

5.1.0 (2023-10-05)

Features

• GitHubProjectNotFoundError (#138) (b48e962), closes #137

v5.0.0

BREAKING CHANGES

• When a field could not be found, the message on the
  thrown error looked like this

  [github-project] "NOPE" could not be matched with any of the existing
  field names: "Title", "Assignees", "Status", "Labels", "Linked pull
  requests", "Reviewers", "Repository", "Milestone", "Text", "Number",
  "Date", "Single select", "Iteration". If the field should be considered
  optional, then set it to "nope: { name: "NOPE", optional: true}

  it is now

  Project field cannot be found

  The original message can still be retrieved using
  error.toHumanMessage()

• When a user value cannot be matched with a field
  option, the message on the thrown error looked like this

  [github-project] "unknown" is an invalid option for "Single select"

  it is now

  Project field option cannot be found

  The original message can still be retrieved using
  error.toHumanMessage()

• if a user tried to update a read-only field, the
  message on the thrown error looked like this

  [github-project] Cannot update read-only fields: "Assignees"
  (.assignees)

  it is now

  Project read-only field cannot be updated

Features

• GitHubProjectError
• GitHubProjectUnknownFieldError
• GitHubProjectUnknownFieldOptionError
• GitHubProjectUpdateReadOnlyFieldError

(#132) (9437ed7)

v4.0.0

4.0.0 (2023-08-20)

Bug Fixes

• deps: update @octokit to latest' (#131) (f4c7bb6)

BREAKING CHANGES

• deps: Node 16 is no longer officially supported, as @octokit
  dropped support as well. Node 16 will be out of maintenance on September
  11, see https://nodejs.dev/en/about/releases/

v3.3.7

3.3.7 (2023-08-20)

Bug Fixes

• revert update of @octokit/core is it drops Node 16 support (#129) (30c0c3c), closes #125

v3.3.6

3.3.6 (2023-08-04)

Bug Fixes

• handle unset item.content (#127) (25f5fa5), closes #126