Skip to content

ci: publish as ezhttp on the hub #63

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ngngardner merged 2 commits into from
Oct 27, 2026
Merged

ci: publish as ezhttp on the hub #63

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3246b9e
ci: publish as ezhttp on the hub
ngngardner Oct 27, 2026
2ea9792
docs: import what the multipart form example uses
ngngardner Oct 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/workflows/publish.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
name: publish

# Publish an existing release tag to the Bend hub as emerging-ezhttp@X.Y.Z.0 by hand,
# Publish an existing release tag to the Bend hub as ezhttp@X.Y.Z.0 by hand,
# e.g. to retry a release whose automatic publish failed. Releases are
# published automatically by release-please.yml. dry-run runs every check
# (proof gate, LICENSE, the hub's name check) and stops before the upload.
Expand All @@ -26,7 +26,7 @@ jobs:
uses: Emerging-Patterns/actions/.github/workflows/publish.yml@73b2fbc64cefd6e22bd786437adb5f35190ee837
with:
tag: ${{ inputs.tag }}
hub-name: emerging-ezhttp
hub-name: ezhttp
dry-run: ${{ inputs.dry-run }}
secrets:
bend-key: ${{ secrets.BEND_HUB_KEY }}
4 changes: 2 additions & 2 deletions .github/workflows/release-please.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ name: release-please

# release-please opens the release PR from conventional commits; merging it
# tags vX.Y.Z and creates the GitHub release. The publish job then sends that
# tag to the Bend hub as emerging-ezhttp@X.Y.Z.0: the shared publish workflow runs the
# tag to the Bend hub as ezhttp@X.Y.Z.0: the shared publish workflow runs the
# proof gate and refuses a package with no LICENSE beside its entry before it
# uploads, since an upload is public and permanent. BEND_HUB_KEY is the Bender
# login of the account that owns the hub name.
Expand Down Expand Up @@ -38,6 +38,6 @@ jobs:
uses: Emerging-Patterns/actions/.github/workflows/publish.yml@73b2fbc64cefd6e22bd786437adb5f35190ee837
with:
tag: ${{ needs.release-please.outputs.tag_name }}
hub-name: emerging-ezhttp
hub-name: ezhttp
secrets:
bend-key: ${{ secrets.BEND_HUB_KEY }}
58 changes: 31 additions & 27 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,14 +11,14 @@ ezhttp is built and checked on bend 2.0.38.
With [Bend](https://github.com/bendlang/bend) alone there is no install
step: import ezhttp by its hub name and `bend` fetches it from
[the hub](https://hub.bend-lang.com) into `~/.bend/lib` on the first run.
`emerging-ezhttp@0.13.0.0` is ezhttp v0.13.0:
`ezhttp@0.22.0.0` is ezhttp v0.22.0:

```
import emerging-ezhttp@0.13.0.0/main.bend as Http
import ezhttp@0.22.0.0/main.bend as Http
```

That name resolves to `0xd3f9c1f02240edb63fd4a109ceb8fa74`.
To pin by content instead, import `0xd3f9c1f02240edb63fd4a109ceb8fa74/main.bend`.
That name resolves to `0xedb2120a04a47dc18c3a756ec7c62750`.
To pin by content instead, import `0xedb2120a04a47dc18c3a756ec7c62750/main.bend`.

Or with [ez](https://github.com/Emerging-Patterns/ez), which records the
package in `ez.toml` (`ez init` makes one):
Expand Down Expand Up @@ -72,9 +72,9 @@ def status_and_text(r: Client.Response) -> String:
```

```
import emerging-ezhttp@0.13.0.0/main.bend as Http
import emerging-ezhttp@0.13.0.0/src/client.bend as Client
import emerging-ezhttp@0.13.0.0/src/body.bend as Body
import ezhttp@0.22.0.0/main.bend as Http
import ezhttp@0.22.0.0/src/client.bend as Client
import ezhttp@0.22.0.0/src/body.bend as Body

def main() -> IO(Client.Response):
Http.http.get("https://example.com/")
Expand Down Expand Up @@ -128,10 +128,10 @@ length from the body. Every other header is sent as you gave it, in order
(SPEC.md HTTP-CLI-8).

```
import emerging-ezhttp@0.13.0.0/main.bend as Http
import emerging-ezhttp@0.13.0.0/src/client.bend as Client
import emerging-ezhttp@0.13.0.0/src/http.bend as Msg
import emerging-ezhttp@0.13.0.0/src/body.bend as Body
import ezhttp@0.22.0.0/main.bend as Http
import ezhttp@0.22.0.0/src/client.bend as Client
import ezhttp@0.22.0.0/src/http.bend as Msg
import ezhttp@0.22.0.0/src/body.bend as Body

def ingest(url: String, json: String) -> IO(Client.Response):
Http.http.post_opts(url,
Expand All @@ -153,7 +153,11 @@ content is `Bytes` (bend-kit-files' `read_bytes`, for example) and is sent
unchanged; the builder searches it for the delimiter with `Bytes.find`.

```
import emerging-ezhttp@0.8.0.0/src/form.bend as Form
import bend-kit-bytes@0.3.2.0/bytes.bend as Bytes
import ezhttp@0.22.0.0/main.bend as Http
import ezhttp@0.22.0.0/src/client.bend as Client
import ezhttp@0.22.0.0/src/http.bend as Msg
import ezhttp@0.22.0.0/src/form.bend as Form

def upload(url: String, key: String, f: Form.Form) -> IO(Client.Response):
match f:
Expand Down Expand Up @@ -208,9 +212,9 @@ It answers a `Server.Answer`: `text_reply(status, headers, body)` (UTF-8),
written in flat memory. The plain serves are these with a text handler.

```
import emerging-ezhttp@0.19.0.0/main.bend as Http
import emerging-ezhttp@0.19.0.0/src/server.bend as Server
import emerging-ezhttp@0.19.0.0/src/http.bend as Msg
import ezhttp@0.22.0.0/main.bend as Http
import ezhttp@0.22.0.0/src/server.bend as Server
import ezhttp@0.22.0.0/src/http.bend as Msg

# echo the body back byte for byte, with the context in a header
def echo(tag: String, req: Server.Req) -> Server.Answer:
Expand All @@ -227,8 +231,8 @@ A handler that needs IO (a file, a subprocess, an upstream call) goes to
service; it is `@unsafe` recursion, so a program calling it is not proof-clean.

```
import emerging-ezhttp@0.13.0.0/main.bend as Http
import emerging-ezhttp@0.13.0.0/src/http.bend as Msg
import ezhttp@0.22.0.0/main.bend as Http
import ezhttp@0.22.0.0/src/http.bend as Msg

def handle(req: Msg.Request) -> Msg.Reply:
match req:
Expand All @@ -242,8 +246,8 @@ def main() -> IO(Unit):
```

```
import emerging-ezhttp@0.13.0.0/main.bend as Http
import emerging-ezhttp@0.13.0.0/src/http.bend as Msg
import ezhttp@0.22.0.0/main.bend as Http
import ezhttp@0.22.0.0/src/http.bend as Msg

def handle(req: Msg.Request) -> IO(Msg.Reply):
match req:
Expand All @@ -260,10 +264,10 @@ def main() -> IO(Unit):
Cookies, `Cache-Control`, and CORS are pure helpers on the same messages.

```
import emerging-ezhttp@0.13.0.0/main.bend as Http
import emerging-ezhttp@0.13.0.0/src/http.bend as Msg
import emerging-ezhttp@0.13.0.0/src/cookie.bend as Cookie
import emerging-ezhttp@0.13.0.0/src/cors.bend as Cors
import ezhttp@0.22.0.0/main.bend as Http
import ezhttp@0.22.0.0/src/http.bend as Msg
import ezhttp@0.22.0.0/src/cookie.bend as Cookie
import ezhttp@0.22.0.0/src/cors.bend as Cors

def authed() -> Msg.Header:
Http.basic("user", "pass")
Expand All @@ -279,8 +283,8 @@ def cross(cfg: Cors.Cfg, req: Msg.Request, reply: Msg.Reply) -> Msg.Reply:
```

```
import emerging-ezjson@1.2.0.0/main.bend as Ezjson
import emerging-ezjson@1.2.0.0/src/value.bend as Value
import ezjson@1.2.0.0/main.bend as Ezjson
import ezjson@1.2.0.0/src/value.bend as Value

def read.of(got: Maybe<&2, Value.Json>) -> Maybe<&2, String>:
match got:
Expand All @@ -300,7 +304,7 @@ byte in upper-case hex, and `/` stays in a path but is `%2F` in a component.
SPEC.md lists these guarantees (HTTP-URL). They are new after ezhttp 0.9.0.

```
import emerging-ezhttp@0.13.0.0/main.bend as Http
import ezhttp@0.22.0.0/main.bend as Http

def search(q: String) -> String:
"https://example.com/search?q=" ++ Http.quote_component(q)
Expand All @@ -324,7 +328,7 @@ and blank values included), and `query_get(pairs, name)` answers the last
value for a name (HTTP-QS). They are new after ezhttp 0.14.0.

```
import emerging-ezhttp@0.15.0.0/main.bend as Http
import ezhttp@0.22.0.0/main.bend as Http

def page(query: String) -> Maybe<&2, String>:
Http.query_get(Http.parse_query(query), "page")
Expand Down
Loading