`ipm publish --dry-run` publishes something

Lukas · March 10, 2026, 8:05pm

Bug report

I wanted to test if everything is alright with my plugin before publishing it, so I executed the publish command with the --dry-run option. Even though the description says that it wouldn’t actually publish, the activity feed of the plugin registry was updated, showing an entry that linked to a nonexistent plugin.

Environment

Platform: Windows
Platform version: 11
App Version: 6.0.0-canary.12

craftzdog · March 11, 2026, 1:37am

Oops, the flag check was missing in the discord feed logic. Thanks!

Lukas · March 11, 2026, 7:56pm

I don’t want to unnecessarily bump this topic, but it seems that this is either not deployed or really fixed as it happend again when using --dry-run

craftzdog · March 12, 2026, 1:39am

Found a bug. The dryrun flag applies only to new packages. Wil fix it. Thanks!

github.com/inkdropapp/ipm

src/commands/publish.ts?plain=1

a84605874


      
            // 404 means package doesn't exist, so it's a new package
          }
          
          // Prepare form data
          const form = new FormData()
          form.append('tarball', await fs.readFile(filePath), {
            filename: path.basename(filePath),
            contentType: 'application/gzip'
          })
          
          if (isNewPackage) {
            form.append('repository', repositoryId)
            form.append('dryrun', dryrun ? 'true' : 'false')
          }
          
          // Determine the endpoint
          const endpoint = isNewPackage ? `` : `/${pkg.name}/versions`
          
          logger.info(`Uploading to ${endpoint}...`)
          
          try {

craftzdog · March 12, 2026, 1:47am

Fixed it in @inkdropapp/ipm-cli@1.0.3. Thanks!