gleam-lang/gleam

Unable to provide alternative hexpm credentials for `gleam publish`

Open

#4,318 opened on Mar 9, 2025

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Rust (960 forks)batch import
good first issuehelp wanted

Repository metrics

Stars
 (21,417 stars)
PR merge metrics
 (Avg merge 10d 19h) (69 merged PRs in 30d)

Description

If you have already authenticated and saved a local token for Gleam to interact with the hex api, it is impossible to provide alternative user/pass credentials when publishing a package.

Attempting to publish a package by setting HEXPM_USER and HEXPM_PASS variables results in the following error:

error: Failed to decrypt data

A problem was encountered decrypting data.
The error from the encryption library was:

    Decryption failed

Steps to reproduce:

  • Generate a local hex token for a hexpm account using gleam hex authenticate
  • Run HEXPM_USER=a_different_account HEXPM_PASS=****** gleam publish
  • Observe the error above.

Contributor guide

Research direction
Examine the hex authentication module to understand how local tokens are stored and how environment variables for credentials are processed. Trace the path where a stored token conflicts with env provided credentials, and pinpoint where decryption fails.
Tech stack
rust
Domain
cli
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60