feat: SDK update for version 18.3.0

[ChiragAgg5k]

This PR contains updates to the SDK for version 18.3.0.

What's Changed

• Added: optional interval parameter on Functions.create, Functions.update and Projects.createSchedule
• Updated: schedule is optional on Projects.createSchedule; pass either schedule or interval
• Added: interval on the Function and Schedule models, functionsIntervalMinimum on BillingPlan

[hansi-codes]

🔵 Tier A · Mergeable after minor fixes

The changes have two minor issues: schedule creation accepts neither scheduling mode, and the updated examples combine mutually exclusive modes.

This release updates the console SDK to version 18.3.0 and adds interval scheduling parameters for functions and project schedules. It also exposes interval and billing minimum metadata in the models and updates the associated examples and release documentation.

Verdict	New comments	Fixed	Still open
💬 Commented	2	0	0

Note

Not approving while a bug finding is open: Require at least one scheduling mode

	Finding	Where
🟡	Require at least one scheduling mode	src/services/projects.ts:584
🟡	The example combines mutually exclusive schedule options	docs/examples/projects/create-schedule.md:17

Fix with agent prompt

### Issue 1
src/services/projects.ts:584
**Require at least one scheduling mode**

With both `schedule` and `interval` optional, a call that omits both passes the remaining local checks and sends a request without a scheduling mode. The documented contract requires one or the other, so this now defers the missing-parameter error to the API; please validate that at least one is provided.

### Issue 2
docs/examples/projects/create-schedule.md:17
**The example combines mutually exclusive schedule options**

This example sends both `schedule` and `interval`, even though the method documentation says they cannot be combined, so copying it produces a rejected request. The function create and update examples have the same combination; please show only one scheduling mode in each example.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

📂 Walkthrough · 10

File	Change
CHANGELOG.md	Documents the 18.3.0 scheduling and model additions.
README.md	Updates the CDN example to use version 18.3.0.
docs/examples/functions/create.md	Adds the interval parameter to the function creation example.
docs/examples/functions/update.md	Adds the interval parameter to the function update example.
docs/examples/projects/create-schedule.md	Adds interval to the project schedule example and marks schedule optional.
package.json	Bumps the package version to 18.3.0.
src/client.ts	Updates the SDK version header.
src/models.ts	Adds interval and billing interval minimum fields to models.
src/services/functions.ts	Adds interval support to function create and update methods.
src/services/projects.ts	Adds interval support and makes schedule optional for schedule creation.

---

_{Reviewed 37b2645 · Details · Comment @hansi-codes review to re-run, or mention @hansi-codes with a question.}

[hansi-codes]

🔵 Tier A · See the inline comments. Summary

[hansi-codes]

Require at least one scheduling mode

With both schedule and interval optional, a call that omits both passes the remaining local checks and sends a request without a scheduling mode. The documented contract requires one or the other, so this now defers the missing-parameter error to the API; please validate that at least one is provided.

Prompt To Fix With AI

This is a comment left during a code review.
Path: src/services/projects.ts
Line: 584

Comment:
**Require at least one scheduling mode**

With both `schedule` and `interval` optional, a call that omits both passes the remaining local checks and sends a request without a scheduling mode. The documented contract requires one or the other, so this now defers the missing-parameter error to the API; please validate that at least one is provided.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{🟡 Minor · bug · Reply if this doesn't apply.}

[hansi-codes]

The example combines mutually exclusive schedule options

This example sends both schedule and interval, even though the method documentation says they cannot be combined, so copying it produces a rejected request. The function create and update examples have the same combination; please show only one scheduling mode in each example.

Prompt To Fix With AI

This is a comment left during a code review.
Path: docs/examples/projects/create-schedule.md
Line: 17

Comment:
**The example combines mutually exclusive schedule options**

This example sends both `schedule` and `interval`, even though the method documentation says they cannot be combined, so copying it produces a rejected request. The function create and update examples have the same combination; please show only one scheduling mode in each example.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{🟡 Minor · documentation · Reply if this doesn't apply.}

[ChiragAgg5k]

@hansi-codes please approve

[hansi-codes]

I can’t approve this as-is; both findings remain valid:

• createSchedule accepts neither schedule nor interval and sends the request without either mode (implementation). The contract requires one.
• The examples provide both mutually exclusive options: project schedule, function create, and function update.

Please validate that one mode is supplied and update the examples to show only one.