public primaryGuild: UserPrimaryGuild | null;
#discord.js (monorepo)
1 messages ยท Page 7 of 1
Random thought: what if we make PrimaryGuild as a class which has these properties? Then we could include a getter to the guild.
Would we then also duplicate the guildTagBadgeURL method there? It's currently directly on the User class
I think UserPrimaryGuild helps avoid confusion that it's related to Guild
That's the description for every hash parameter in this class
I'd say it's superfluous.
db8c1d3 fix: background on pages with little content (#... - almeidx
9708717 fix(api-extractor): links including entrypoints... - Qjuh
8e03af6 feat: update @types/node to v22 (#10926) - almeidx
4e0beff types(ClientEventTypes): add missing guildSoun... - sdanialraza [2852a52`](https://github.com/discordjs/discord.js/commit/2852a529cf8618e49c18c897feef279659b96b76) docs: update param wording for consistency (#10... - Crytek1012
Hello there, i'm came here to appeal since is been months or idk maybe a year, i wanna an appeal if i did like some mistakes of switch accounts, if i'm not quite that Good remembering! But i wanna came back to the server just everything changed! Also wanna actually came back for the main server for helping, for an friendly conversation, and for contributing the library itself!
Here my id: 1202432891100069898
Reason for banned: switch between accounts
Question: if i'm not quite sure but I r...
[discordjs/discord.js] New branch created: build/bump-discord-api-types
e2da15f build: bump discord-api-types to 0.38.15 - sdanialraza
Please describe the changes this PR makes and why it should be merged:
Status and versioning classification:
[discord.js] Branch feat/add-primary-guild was force-pushed to `cae2a68`
When are we automating these pull requests? ๐
[discordjs/discord.js] New branch created: chore/bump-deps
- The docgen package was missing the
terserdependency, which is being used by tsup - Removed
jestfrom discord.js. There was only one test using it, and there wasn't even a test script on package.json. It was the only package with the dependency - Added
vitest.config.tsto the dependencies of thetestturbo task
Why was this not under a semver range again?
Lets move all major bumps to a separate PR
Not really, 65.0.0 is 0.65, they just switched away from 0ver
[discord.js] Branch feat/add-primary-guild was force-pushed to `1f464ef`
Didn't we want to remove this dependency and use --env-file instead?
if a patch call doesn't include primary_guild this will unset it although it should remain unchanged. Same applies to avatar_decoration_data though, no idea if that was discussed for that before. Imho it should get the same treatment as banner or accent_color did, unless we got something that guarantees this behaves differently.
Copy paste mistake ๐
Even if we did, its out of scope for this PR and should be done in a separate one please
If it can happen, the if check should check key in data
[discordjs/discord.js] New branch created: docs/dapi-removal
This used to serve a purpose.
This will now cause a payload of {avatar_decoration_data: null} to cause User#avatarDecorationData to be {asset: undefined, skuId: undefined} which is not valid according to the types. So should probably keep both the in check and the value is falsey.
[discordjs/discord.js] New branch created: legacy-guide
Is your feature request related to a problem? Please describe.
It would be nice to have some examples on how to create scheduled events and polls without having to piece it together from the documentation.
Describe the solution you'd like
It would be nice to have some examples on how to create scheduled events and polls without having to piece it together from the documentation.
Describe alternatives you've considered
No response
Additional notes
No response
Is your feature request related to a problem? Please describe.
It took me way too long to figure out that to communicate between shards (i.e. to have one shard communicate something to all other shards) is done by making use of manager.broadcast and process.on. This info is not available in the chapter about shard communication.
Describe the solution you'd like
Information or a code sample that roughly goes like th...
The reason is not that you switched accounts, but the fact that switching became necessary because of negligence and not wanting to bother with properly remediating the situation for your initial account. As a public community, we have identified this as risk to our members and have removed all involved accounts as a result.
As mentioned in the original appeal request, we will not be granting appeals for this moderation action.
Please note that re-joining Discord servers on alt accounts...
how to make this discord embed new ui and put the buttons and select menu inside the embed box with seperating them
These are not embeds, but components: https://discordjs.guide/popular-topics/display-components.html
Please describe the changes this PR makes and why it should be merged:
This is a very early proof-of-concept stage to discuss how @discordjs/structures might get implemented in next discord.js version.
Status and versioning classification:
5b7d0f6 build: bump discord-api-types to 0.38.16 - Jiralite
4dbeed9 chore(WebSocketShard): improve zlib-sync errors... - LJNeon
a5bd4cf feat!: use zod v4 (#10922) - almeidx
e6d59ea types(ReadonlyCollection): derivation logic (#1... - Renegade334
42fbca8 types: reverse interface inheritance to omit Om... - Qjuh
024ae5c build: bump discord-api-types to 0.38.15 (#10966) - sdanialraza
9fc3e5e fix: Adjust reason in methods options (#10977) - Jiralite
1404e32 fix(Events): WebhooksUpdate enum value (#10970) - Qjuh
51ceb20 fix(DirectoryChannel): Export class (#10985) - Jiralite
d4f742e refactor(ThreadChannel): Remove trimming of nam... - Jiralite
9047827 Merge branch 'v14' into refactor/deprecate-ready - Jiralite
040c66a docs(ApplicationCommand): incorrect method in e... - sdanialraza
500712d types(ModalSubmitFields): fix fields type (#1... - sdanialraza
b36b751 fix(Message): forwarded messages are not cross... - almeidx [5be774d](https://github.com/discordjs/discord.js/commit/5be774db641b60669505645861d721200d335a7b) docs: remove hardcoded locale from links (#10794) - almeidx [63f5261`](https://github.com/discordjs/discord.js/commit/63f5261f4c351cd1b6befca1163254300f7424f4) fix(GuildChannelManager): properly resolve avat... - imnaiyar
[discordjs/discord.js] New branch created: feat/animated-webp
f45615e feat: Support animated WebP (#10911) - Jiralite
What happens if you provide both?
"https://cdn-discord.com/emojis/123456.gif?animated=true".
It should be noted that the typings disallow this:
No overload matches this call.
Overload 1 of 2, '(emojiId: string, options?: Readonly<EmojiURLOptions> | undefined): string', gave the following error.
Object literal may only specify known properties, and 'animated' does not exist in type 'Readonly<EmojiURLOptionsNotWebp>'.
Overload 2 of 2, '(emojiId: string, extension?: "gif" | "webp" | "png" | "jpg" | "jpeg"...
Discord Guild Member Update Implementation
Current Status
Discord hasn't released an official update for this feature yet, but there's a workaround available.
Implementation Method
You can use the following approach to listen for guild member updates:
client.ws.on(GatewayDispatchEvents.GuildMemberUpdate, async (data) => {
console.log(data)
});
Example Repositories
1. sw3do/discord-tag-role-bot
Repository: https://github.com/sw3do/...
de2b2dd chore: bump dependencies (#10967) - almeidx
8a36c42 fix(DirectoryChannel): Export class (#10985) - Jiralite
7e3d4e5 refactor(ThreadChannel): Remove trimming of nam... - Jiralite
1105ec9 feat(channel)!: New pinned messages routes (#10... - Jiralite
85d8231 Merge branch 'main' into feat/add-collectibles - sdanialraza
[discordjs/discord.js] New branch created: build/14-bump
Upgrades discord-api-types for v14.
[discordjs/discord.js] New branch created: build/ws-upgrade
ee3ca6f refactor(create-discord-bot): replace deps with... - SuperchupuDev
bc6005f feat(guide): port legacy guide (#10938) - almostSouji
7242352 feat!: role gradient colors (#10961) - sdanialraza
35cc57a fix: Adjust reason in methods options (#10976) - Jiralite
1f0fe39 refactor(CDN)!: Use an object for the construct... - Jiralite
* @property {?Snowflake} identityGuildId The id of the user's primary guild
* @property {?boolean} identityEnabled Whether the user is displaying the primary guild's tag
* @property {?string} tag The user's guild tag. Limited to 4 characters
* @property {?string} badge The guild tag badge hash
[discordjs/discord.js] New branch created: feat/new-pinned-messages-routes
We've decided to grant the appeal.
Please reconsider how you approach discussing issues you feel passionate about going forward.
9ff0482 feat: support user guilds (#10962) - sdanialraza
[discordjs/discord.js] New branch created: fix/context-validate-none
a5bd4cf feat!: use zod v4 (#10922) - almeidx
e6d59ea types(ReadonlyCollection): derivation logic (#1... - Renegade334
42fbca8 types: reverse interface inheritance to omit Om... - Qjuh
024ae5c build: bump discord-api-types to 0.38.15 (#10966) - sdanialraza
ee3ca6f refactor(create-discord-bot): replace deps with... - SuperchupuDev
[discordjs/discord.js] New branch created: feat/support-user-guilds
43ddc19 feat: support user guilds - sdanialraza
Please describe the changes this PR makes and why it should be merged:
Backports #10962
Status and versioning classification:
- Code changes have been tested against the Discord API, or there are no code changes
- I know how to update typings and have done so, or typings don't need updating
- This PR changes the library's interface (methods or parameters added)
[discordjs/discord.js] New branch created: fix/regex-removal-context
[discordjs/discord.js] New branch created: fix/invite-fields-null
[discordjs/discord.js] New branch created: refactor/remove-rest-option
3ef3680 refactor(WebSocketManager)!: remove deprecated ... - almeidx
BREAKING CHANGE: The rest option in the WebSocketManager constructor has been removed. Pass a fetchGatewayInformation function instead.
[discordjs/discord.js] New branch created: fix/container-v10
I would love it if you could alphabetise this!
Have we merged any other major ws PRs?
Shouldn't this still error if no fetchGatewayInformation function was passed? Considering the types only guarantee this for ts users, not runtime.
Have we merged any other major ws PRs?
I know you didn't write this comment but literally what does it mean? We use it to fetch more than the gateway URL; it also doesn't default to anything anymore
I guess it should say "Function to be used when fetching /gateway/bot. We recommend using a REST client that respects Discord's rate limits"
I know you didn't write this comment but literally what does it mean? We use it to fetch more than the gateway URL; it also doesn't default to anything anymore
One could guess it is referring to websocket proxy?
[discordjs/discord.js] New branch created: refactor/brokers-require-consumer-name
[discordjs/discord.js] New branch created: feat/brokers-built-in-random-group
[discordjs/discord.js] New branch created: feat/brokers-find-dead-events
[discordjs/discord.js] New branch created: feat/brokers-poll-dead-consumers
[discordjs/discord.js] New branch created: feat/redis-broker-core-gateway-impl
Being superseded by #11005
5d16197 feat(ws,rest): totally new features - didinele
[discordjs/discord.js] New branch created: feat/totally-a-new-feature
Thank you for the response will try this right away! ๐
You are welcome. Im waiting your response! <3
a0f8da2 docs: Add structures to main - Jiralite
[discordjs/discord.js] New branch created: docs/structures-main
Adds @discordjs/structures to the main README.md with the other packages.
3a060f7 docs: Replace Discord API with Discord Develope... - Jiralite
Please describe the changes this PR makes and why it should be merged:
Status and versioning classification:
Please describe the changes this PR makes and why it should be merged:
Status and versioning classification:
Dear @iikeeeer
Can you stop doing spam issues
Thanks
[discordjs/discord.js] New branch created: fix/guild-create-removal
36a82c3 fix: remove guild creation - Jiralite
Please describe the changes this PR makes and why it should be merged:
Per https://discord.com/developers/docs/change-log#deprecating-guild-creation-by-apps, the endpoint is no longer available.
Status and versioning classification:
- Code changes have been tested against the Discord API, or there are no code changes
- I know how to update typings and have done so, or typings don't need updating
- This PR includes breaking changes (methods removed or renamed, parameters moved...
[discordjs/discord.js] New branch created: ci/release-fixes
- Added @discordjs/structures
- Corrected
ssh_keytossh-key - Running with Node.js 22
aee6d31 fix(Container): Use the same discord-api-types ... - Jiralite
43a995b refactor!: Invite classes (#10888) - Jiralite
a7f711b fix: Remove trailing color references (#11007) - Jiralite
3a060f7 docs: Replace Discord API with Discord Develope... - Jiralite
90b3692 docs: Add structures to main README.md (#11008) - Jiralite
08a61ca refactor(WebSocketManager)!: remove deprecated ... - almeidx
c0c1ac2 ci(release): Miscellaneous fixes (#11014) - Jiralite
Fixes messed up removal of strategy from rebase and adds description for input
deba30a chore: add more partials - Jiralite
[discordjs/discord.js] New branch created: chore/issue-partials-update
More partials are possible from:
- #10590
- #10328
[discordjs/discord.js] New branch created: fix/remove-guild-ownership-stuff
Which application is this bug report for?
Guide
Issue description
hello there, i'm was about to run pnpm build:apps, yet i got confused, from this
Steps to Reproduce
1: Run the app Website
2:check if everything fine and even normal with changes
3:didn't understand this one but here just to sent my issue
Versions
- version: 14.21.0
Issue priority
Low (slightly annoying)
- why did you want to run that script in particular?
- did you follow the steps mentioned in CONTRIBUTING.md file, i.e.
pnpm run buildbefore?
Yes i did! I did all what it says! And i got confused why it didn't work
Then why did you try to run build:apps separately? And we can't really help with the vague description of "confused". Nor is this the place to help with questions, that would be our discord server.
Please describe the changes this PR makes and why it should be merged:
TypeScript rewrite of the discord-rpc library moved to the monorepo
Status and versioning classification:
- Code changes have been tested against the Discord API, or there are no code changes
- I know how to update typings and have done so, or typings don't need updating
[discordjs/discord.js] New branch created: fix/deprecate-guild-owner-methods
[discordjs/discord.js] New branch created: feat/guild-template-create
Missing stuff:
https://github.com/discordjs/discord.js/blob/943c39e4c068447c9...
rpc code is licensed MIT and has several contributors. you'll need to either keep the MIT license or reach out to them all to relicense it.
Wouldn't it be easier to keep RPC MIT licensed?
Unsure if the stylistic preference is to remove this directory (which is fine). @vladfrangu @almeidx
Will this package realistically have tests? If not, I'd rather get rid of the folder, script and test-related dependencies
Hard to test RPC without mocking a lot of obscure whoknowswhats, i'm ok with dropping tests
[discordjs/discord.js] New branch created: chore/deno-vsc
[discordjs/discord.js] New branch created: build/lock-update
9261170 build: upgrade pnpm-lock.yaml - Jiralite
Please describe the changes this PR makes and why it should be merged:
Still need to set a user....
Status and versioning classification:
Is contents: write still needed for permissions since the application has permission-contents: write and will be doing the work?
We could have this use the application token too!
9be62b3 chore: Update deno.unstable to an array (#11032) - Jiralite
Can probably become read as long as provenance doesn't need write
Don't know if provenance supports that, we could try though?
I believe it does need it, but since GITHUB_TOKEN will be that from actions/create-github-app-token, it should be fine since permission-contents: write is present.
provenance appears to be unrelated to the token itself, but merely requesting the perm will set the required env vars
c3dc581 fix: attachment sending (#11015) - almeidx
8f5ac55 fix!: Remove API related to guild ownership (#1... - Jiralite
a2ee393 fix(guild): Creating a template actually create... - Jiralite
698b92c fix(guild)!: Remove API related to guild owners... - Jiralite
bdcb3e1 build: Upgrade pnpm-lock.yaml (#11036) - Jiralite
1014af3 chore: Add more partials to issue form (#11018) - Jiralite
fdc305d ci: Use actions/checkout@v5 (#11040) - Jiralite
[discordjs/discord.js] New branch created: build/fix-package-name-arg
d81ed27 build: fix package name argument parsing - almeidx
program.args is empty if no arguments are passed via CLI, despite us passing a default value.
program.processedArgs seems to work as we expect.
[discord.js] Branch build/fix-package-name-arg was force-pushed to `919ad96`
Please describe the changes this PR makes and why it should be merged:
apparently commitish is not so ish
Status and versioning classification:
1fb297b chore: Remove classification labelling - Jiralite
[discordjs/discord.js] New branch created: Jiralite-patch-1
[discordjs/discord.js] New branch created: chore/bump-djs-in-cdb
Any reason for not bumping typescript here, in -utils and voice?
Probably should include an expires_at in the test payload instead.
My filter was too wide for filtering out api-extractor it seems
As for voice, it's stuck on that version due to array buffer changes. Would need to make changes to source
Including expires_at: null still fails, as .toJSON() doesn't include it. At least that's what it appeared to be at a glance, didn't look into it
well it's a good thing this test indicates a failure based on that api change then, since it isn't technically properly recreating the payload
[discordjs/discord.js] New branch created: fix/consider-everyone-base
[discordjs/discord.js] New branch created: fix/remove-guild-ownership-stuff
a2ee393 fix(guild): Creating a template actually create... - Jiralite
698b92c fix(guild)!: Remove API related to guild owners... - Jiralite
bdcb3e1 build: Upgrade pnpm-lock.yaml (#11036) - Jiralite
9be62b3 chore: Update deno.unstable to an array (#11032) - Jiralite
ac290ae ci(release): use app user (#11038) - ckohen
498d323 build: bump discord-api-types - Jiralite
Please describe the changes this PR makes and why it should be merged:
Status and versioning classification:
- Code changes have been tested against the Discord API, or there are no code changes
- I know how to update typings and have done so, or typings don't need updating
- This PR changes the library's interface (methods or parameters added)
[discordjs/discord.js] New branch created: ci/fix-bad-name
d9d8642 ci(pr-triage): fix bad name merge - Jiralite
Imagine this scenario:
- A user opens a pull request that is out of date with main. The pull request title does not match the regular expression
- The user updates their branch
When the user updates their branch, synchronisation occurs. This means validation will be skipped, and the error will go away. This means a bad actor could merge a pull request with any name they like if the pull request was in an approved state.
This pull request makes validation always run.
Even if this runs more than itโs supposed to, itโs not like this is an โexpensiveโ job
[discordjs/discord.js] New branch created: refactor/remove-fetch-voters
This can be fixed in a follow-up pull request to /structures
cde757b ci(pr-triage): Make validate title run always (... - Jiralite
5001897 feat: add email and phoneNumber formatters ... - almeidx
d548a59 fix(Guild)!: Remove setting owner (#11068) - Jiralite
368edea fix(rest): emit warning on HTTP 401 with non-ze... - ckohen
cde757b ci(pr-triage): Make validate title run always (... - Jiralite
cc43dad chore: bump dependencies (#11051) - almeidx
5001897 feat: add email and phoneNumber formatters ... - almeidx
d548a59 fix(Guild)!: Remove setting owner (#11068) - Jiralite
368edea fix(rest): emit warning on HTTP 401 with non-ze... - ckohen
cde757b ci(pr-triage): Make validate title run always (... - Jiralite
cc43dad chore: bump dependencies (#11051) - almeidx
[discordjs/discord.js] New branch created: build/same-timestamp-for-releases
04c0872 build: use the same timestamp for release versions - almeidx
Moved the creation of the timestamp part of release versions outside of the loop, so all the versions released in each run will have the same timestamp. This is mostly a QoL change for people (me) when upgrading packages.
e.g., this is the way the versions are currently:
{
"dependencies": {
"@discordjs/core": "3.0.0-dev.1756512122-cc43dadca",
"@discordjs/rest": "3.0.0-dev.1756512128-cc43dadca",
"@discordjs/ws": "3.0.0-dev.1756512132-cc43dadca"
}
}
Everythin...
[discordjs/discord.js] New branch created: feat/guest-invites-v14
[discordjs/discord.js] New branch created: refactor/register-actions
b6089e5 build: upgrade discord-api-types to 0.38.22 - Jiralite
215f8dc fix: Do not omit falsy default values (#10755) - Amgelo563
77f7c7f fix: Do not omit falsy default values (#10755) - Amgelo563
e59762b fix: Do not omit falsy default values (#10755) - Amgelo563
437bb94 feat: show default values in docs (#10465) - Qjuh
when does the next release coming with modals updates?
We don't give ETAs for release dates. We very rarely share details prior to release; when they're made they're announced in the Discord server
We don't give ETAs for release dates. We very rarely share details prior to release; when they're made they're announced in the Discord server
Regarding modals, you can track the relevant PRs here:
- #11034
- #11078
- #11081
I think this and stickers could instead be grouped under a "message" label
In general I'd be in favor of less clutter on the labels. Especially like the shorter package labels.
IMO I'd prefer not having prefixes for the remaining labels. The package labels are different since having more than one is common, so it's nice that they are grouped. This is not really the case with the other labels. Not sure what others think about this
I've never seen us use this label. Quick search reveals there are no issues/pull requests with it.
Might as well get rid of it
Is it really that important that we label things as "duplicate"s? Since there are now different types of issue closure types, including one for duplicates (not only that, but still)
Similar to duplicate label
Despite this description not being wrong, I think it could better describe the reasoning behind this label.
How about something like:
description: Pull requests that require more than the usual number of reviewers; blocks automatic merge.
There isn't a whole lot about this specifically. I think it could be grouped under channel
yes
<img width="388" height="218" alt="image" src="https://github.com/user-attachments/assets/b8598a5c-0b50-4d28-a8e7-3b534bab9b10" />
Disregard as it's a separate resource on discord's end
separate resource on Discord's documentation
Ah, that's what you went with.. Didn't realize it
I don't think the label is very self-explanatory and the description as is seems weird.
Perhaps removing "-related" would make it more clear (as you just said in the reply), or adding some more context
Update this too:
I believe Vitest can be removed as a dependency now.
Should this be here? It looks awkward!
Should this be here? It looks awkward!
54880f2 feat: use issue types - Jiralite
48ac00a fix: remove more labels - Jiralite
I'm thinking of our existing api-changes and api support labels. We could rename this label to "t:discord" and then use it for both issues (they opened an issue but it's actually for Discord) and pull requests (the reason for the pull request is a change in Discord). Or, we could have 2 labels: 1 for issues and 1 for pull requests. Thoughts? Thinking how best to say an issue is actually an upstream issue and the reason for a pull request is because Discord changed something (whether that is a...
The Release workflow handles create-discord-bot, but we need it to handle create-discord-app wherever that is done too.
Please describe the changes this PR makes and why it should be merged:
Status and versioning classification:
Please describe the changes this PR makes and why it should be merged:
Status and versioning classification:
[discordjs/discord.js] New branch created: fix/current-member-edit-type
[discordjs/discord.js] New branch created: fix/current-member-edit-type-main
e382d60 build: upgrade discord-api-types to 0.38.24 - Jiralite
Do we need to do something about the license at the root of the monorepo as this license differs from it?
f1bcff4 feat(rest): callbacks for timeout and retry bac... - ckohen
4ec03ae feat!: label component and selects in modal (#1... - imnaiyar
90aac12 fix(users): Correct type for editing current gu... - Jiralite
126529f fix: overflow on package home (#11101) - almeidx
82e4839 Merge branch 'main' into feat/more-labels-in-bu... - Jiralite
[discordjs/discord.js] New branch created: refactor/core-consolidated-options
- #1317206872763404481 message
[discordjs/discord.js] New branch created: feat/builders-modal-label-file
2b07084 build: bump discord-api-types - Jiralite
This example actually isn't valid because max_values defaults to 1. min_values must always be <= max_values.
* The file upload component type is associated with a {@link FileUploadBuilder}.
[discordjs/discord.js] New branch created: feat/modify-self-v14
[discordjs/discord.js] New branch created: fix/edit-me-conditionally
7886d9b feat(GuildMemberManager)!: Add new modify self ... - Jiralite
beed098 fix: Add type to some predicates (#11110) - Jiralite
2d740d5 fix(GuildMember): Use editMe() conditionally ... - Jiralite
b3705df fix: use in operator when resolving modal compo... - imnaiyar
0d76f11 fix: Add idPredicate (#11109) - Jiralite
https://github.com/discordjs/discord.js/blob/9201243f32df4f85218fa36cf52a8ac7420bd791/packages/discord.js/src/structures/GuildChannel.js#L474
The voice channel also requires ViewChannel permission
437692d ci: implement workflow to publish dev versions - didinele
[discordjs/discord.js] New branch created: ci/publish-tagged-dev
The last piece of the puzzle for our GitHub bot.
I'd argue generally a pull request number (and maybe we should even assert it but that's not a blocker)
I guess my main issue with that is like, I don't think I can use the PR number as a ref and resolving it in that CI context seems.. hell-ish? The workflow doesn't really need to be the most human friendly given the goal is to call it via bot.
And also, there's maybe some advantages to the general tag when we're trying to test something special and maybe don't even have a PR.
And I'm guessing the bot will just use pr-<num> as the tag then?
Either way its fine, I'm not too fussed about this, maybe just for us we should use some tags we can easily reference back
Oh, one thing to add: a flow to deprecate all releases with a tag, so once we're done they can be marked as deprecated on npms end ๐
And I'm guessing the bot will just use pr-<num> as the tag then?
I more-so envisioned the tag as an input so we make sure it's coherent & easy to understand what you're actually using in logs that reference VERSION or package.json info, e.g. @bot pack this new-ws-compression
Oh, one thing to add: a flow to deprecate all releases with a tag, so once we're done they can be marked as deprecated on npms end ๐
Errrr, right. I'm not really sure when that would run, though? On PR cl...
It doesn't have to be automatic necessarily/if its hard to do, but sure, whatever works and lets us mark a tag (that is not dev or latest lol) as deprecated
I think you want to use the tag name in the deprecate name
I would argue that the tag name should be something readable, and we pass a ref as well (which can absolutely just be based on the pr number)
Overall looks pretty good, I really don't think this is a separate workflow though. The only reason normal dev releases are is to run on cron.
Please describe the changes this PR makes and why it should be merged:
Makes the Release CI always use the main workflow which allows us to release from branches that don't have the workflow. Doing this in the dev workflow adds an extra layer of security, that will be done in or after #11120
Status and versioning classification:
[discordjs/discord.js] New comment on issue #11083: Select menus and text display support for modals
@Jiralite is there a timeline on expected release for this functionality?
Skipped steps are still shown on the UI on action runs, so this and the following steps should probably have different names (maybe a " (main)" suffix)
Yeah I went by what we had done for the docs runs, but I do think we should name it better. 5e0c8d51c
Is it me, or this description doesn't match the usage?
if: ${{ !inputs.ref || inputs.ref == 'main' }}
...
main: false
Doesn't this also need to use working-directory: ./main for it to use the correct script and for the $.cwd('../'); to actually change the working dir to the correct place?
https://github.com/discordjs/discord.js/blob/f510b5ffabfb22f634876e27e5316db36f9c80b4/packages/actions/src/releasePackages/action.yml#L18
Shouldn't we use working-directory^1 here instead of manually cd'ing?
flipped the logic, thanks
that makes sense, again was following what we had done, but this is cleaner
working directory only works with run, but this brings up I need to check if the working directory is actually what I think it is, will do that shortly, blocking until I do
I should've remembered it from when I was doing the initial testing, but I see what you are saying now. It actually works out really well that the working directory is always the workspace root, cause github gives me all the information I need and I don't actually need to pass down whether we're running from main or not, it just works โข๏ธ
6431cea ci(release): use main action always (#11125) - ckohen
a7f711b fix: Remove trailing color references (#11007) - Jiralite
3a060f7 docs: Replace Discord API with Discord Develope... - Jiralite
90b3692 docs: Add structures to main README.md (#11008) - Jiralite
f2fec91 feat: Enforce limit of URLs for link buttons (#... - Jiralite
6cdfa38 ci: better release workflow (#10325) - ckohen
a7f711b fix: Remove trailing color references (#11007) - Jiralite
3a060f7 docs: Replace Discord API with Discord Develope... - Jiralite
90b3692 docs: Add structures to main README.md (#11008) - Jiralite
f2fec91 feat: Enforce limit of URLs for link buttons (#... - Jiralite
6cdfa38 ci: better release workflow (#10325) - ckohen
[discordjs/discord.js] New branch created: fix/voice-typescript-upgrade
[discordjs/discord.js] New branch created: chore/bump-deps
I would've called this ref, not pull, but sure
But this forces the ref to be a PR, so which is it ๐
Actually, I'd probably agree with that. The description matches that better.
db07a53 ci: bump actions/setup-node to v5 - almeidx
[discordjs/discord.js] New branch created: ci/actions-setup-node-v5
This version has automatic package manager dependencies cache enabled by default, but we have our own implementation of it, so added package-manager-cache: false to disable it.
[discordjs/discord.js] New branch created: feat/add-group-dm-recipient-endpoints
[discordjs/discord.js] New comment on issue #11083: Select menus and text display support for modals
Is there anything I can do to expedite the release of this feature?
[discordjs/discord.js] New branch created: fix/builder-logic-for-select-menu-assertions
[discordjs/discord.js] New branch created: types/use-return-types-instead-of-direct-types
6431cea ci(release): use main action always (#11125) - ckohen
2c750a4 refactor!: make RedisBroker require consumer na... - didinele
cf89260 feat(RedisBroker): poll for unacked events (#11... - didinele
d251e06 feat(RedisBroker): ability to explicitly tell t... - didinele
ffbb7b6 feat: Add gateway endpoints (#11130) - Jiralite
[discord.js] Branch chore/turn-on-curly-again was force-pushed to `8dc1692`
6431cea ci(release): use main action always (#11125) - ckohen
2c750a4 refactor!: make RedisBroker require consumer na... - didinele
cf89260 feat(RedisBroker): poll for unacked events (#11... - didinele
d251e06 feat(RedisBroker): ability to explicitly tell t... - didinele
ffbb7b6 feat: Add gateway endpoints (#11130) - Jiralite
612c49b fix: adjust types for typescript upgrade (#11132) - almeidx
05224e7 fix(builders): correct assertion for select men... - vladfrangu
dee79ef fix: sidebar tab icon (#11141) - almeidx
cf88ef9 types(Webhook): specify message type (#11142) - Pavel-Boyazov
fbdec3d feat!: add escapeQuote and escapeBlockQuote... - almeidx
[discordjs/discord.js] New branch created: ci/release-target-cda
f913b0f ci(release): handling for create-discord-app - didinele
89b5405 ci(deprecate): cda support - didinele
Pull Request Overview
This PR adds support for modal select menus in builders v1 by introducing a new LabelBuilder component and updating the modal system to support both traditional action rows and the new label components. The changes enable developers to create more flexible modal interfaces with labeled form controls.
Key changes:
- Introduces
LabelBuilderfor creating labeled form components in modals - Updates
ModalBuilderto support both action rows and label components - Mo...
The ActionRowBuilder<ModalActionRowComponentBuilder> constructor cannot be passed directly to resolveBuilder as it expects a constructor that can be called with new Constructor(). This will cause a runtime error when the function attempts to instantiate the generic type.
const resolved = normalized.map((row) => resolveBuilder(row, ActionRowBuilder));
Missing file extension in import statement. Should be '../Assertions.js' for consistency with other imports in the codebase.
import { customIdValidator, emojiValidator, idValidator } from '../Assertions.js';
The deprecation message is incorrect. The addActionRowComponents method should suggest using the existing non-deprecated methods for action rows, not addLabelComponents which is for a different component type.
* @deprecated Use {@link ModalBuilder.addComponents} instead
The example code references a setContent method that doesn't exist in the LabelBuilder class. This should likely be setDescription or setLabel based on the available methods.
* }).setLabel('new text');
[discordjs/discord.js] New branch created: fix/guide-misc
[discordjs/discord.js] New branch created: fix/guide-path
d251e06 feat(RedisBroker): ability to explicitly tell t... - didinele
ffbb7b6 feat: Add gateway endpoints (#11130) - Jiralite
612c49b fix: adjust types for typescript upgrade (#11132) - almeidx
05224e7 fix(builders): correct assertion for select men... - vladfrangu
dee79ef fix: sidebar tab icon (#11141) - almeidx
88778df ci: bump actions/setup-node to v5 (#11134) - almeidx
Going to wait for #11146 to merge.
Image:
We will not be reactivating the widget in the server. We should find a replacement badge that doesn't require a widget. If there isn't one, we should remove it.
d045939 ci: update our custom action to handle the rena... - didinele
[discordjs/discord.js] New branch created: chore/update-badge
9b814f6 chore: update readme badges - didinele
The Discord server badge is also included in the readme's of packages, e.g.
https://github.com/discordjs/discord.js/blob/88778df0e5e5963c11f54246e12f7439b64866ba/packages/actions/README.md?plain=1#L8
985b525 chore: bump dependencies (#11133) - almeidx
88778df ci: bump actions/setup-node to v5 (#11134) - almeidx
b80dd8c types(ClientEventTypes): fix messageDeleteBulk... - Pavel-Boyazov [e677959`](https://github.com/discordjs/discord.js/commit/e677959c7fee12116688452e4cf906dc9db3b7cd) Merge branch 'main' into refactor/remove-guide-... - kodiakhq[bot]
7de5b4a refactor: remove guide route prefix (#11146) - almeidx
985b525 chore: bump dependencies (#11133) - almeidx
88778df ci: bump actions/setup-node to v5 (#11134) - almeidx
b80dd8c types(ClientEventTypes): fix messageDeleteBulk... - Pavel-Boyazov [f109fc9](https://github.com/discordjs/discord.js/commit/f109fc9b428999c0b3254838d68bd7468c8988fa) chore(guide): Update name of legacy path (#11149) - Jiralite [7de5b4a`](https://github.com/discordjs/discord.js/commit/7de5b4a349d1769261d6ec41ccac8400b0ecf17d) refactor: remove guide route prefix (#11146) - almeidx
f1087c7 fix: Guide content path for CODEOWNERS (#11148) - Jiralite
b80dd8c types(ClientEventTypes): fix messageDeleteBulk... - Pavel-Boyazov [f109fc9](https://github.com/discordjs/discord.js/commit/f109fc9b428999c0b3254838d68bd7468c8988fa) chore(guide): Update name of legacy path (#11149) - Jiralite [7de5b4a](https://github.com/discordjs/discord.js/commit/7de5b4a349d1769261d6ec41ccac8400b0ecf17d) refactor: remove guide route prefix (#11146) - almeidx [f1087c7](https://github.com/discordjs/discord.js/commit/f1087c7e8717c2b77444eeced07800151a760d6a) fix: Guide content path for CODEOWNERS (#11148) - Jiralite [f4d361c`](https://github.com/discordjs/discord.js/commit/f4d361c12924c7403441a41200165541be9b673d) Merge branch 'main' into fix/ws-re-throw - kodiakhq[bot]
[discordjs/discord.js] New review comment on pull request #10931: chore(lint): turn on `curly` again
if (!collection) {
// runtime check
return false;
}
This and the other unresolved conversations
[discordjs/discord.js] New review comment on pull request #10931: chore(lint): turn on `curly` again
for (const key of Object.keys(yaml).sort((a, b) => a.localeCompare(b))) {
sortedYAML[key] = yaml[key]!;
}
These are not embeds, but components: https://discordjs.guide/popular-topics/display-components.html
[discordjs/discord.js] New branch created: chore/bump-builders-in-v14
88778df ci: bump actions/setup-node to v5 (#11134) - almeidx
b80dd8c types(ClientEventTypes): fix messageDeleteBulk... - Pavel-Boyazov [f109fc9](https://github.com/discordjs/discord.js/commit/f109fc9b428999c0b3254838d68bd7468c8988fa) chore(guide): Update name of legacy path (#11149) - Jiralite [7de5b4a](https://github.com/discordjs/discord.js/commit/7de5b4a349d1769261d6ec41ccac8400b0ecf17d) refactor: remove guide route prefix (#11146) - almeidx [f1087c7`](https://github.com/discordjs/discord.js/commit/f1087c7e8717c2b77444eeced07800151a760d6a) fix: Guide content path for CODEOWNERS (#11148) - Jiralite
612c49b fix: adjust types for typescript upgrade (#11132) - almeidx
05224e7 fix(builders): correct assertion for select men... - vladfrangu
dee79ef fix: sidebar tab icon (#11141) - almeidx
cf88ef9 types(Webhook): specify message type (#11142) - Pavel-Boyazov
fbdec3d feat!: add escapeQuote and escapeBlockQuote... - almeidx
The Discord server badge is also included in the readme's of packages, e.g.
https://github.com/discordjs/discord.js/blob/88778df0e5e5963c11f54246e12f7439b64866ba/packages/actions/README.md?plain=1#L8
I forgot to update the name when taking it from elsewhere, it is a pull number, not an arbitrary ref.
79499e3 fix: don't double release on github - didinele
fbdec3d feat!: add escapeQuote and escapeBlockQuote... - almeidx
2c08b0f feat(thread)!: Add query to getting a thread me... - Jiralite
985b525 chore: bump dependencies (#11133) - almeidx
88778df ci: bump actions/setup-node to v5 (#11134) - almeidx
b80dd8c types(ClientEventTypes): fix `messageDeleteBulk... - Pavel-Boyazov
fcf7f27 ci(release): handling for create-discord-app (#... - didinele
[discordjs/discord.js] New branch created: ci/release-target-cda
aab7222 fix: always use actions from main - didinele
0c2975e ci: implement workflow to publish dev versions ... - didinele
3007d8f ci(documentation): handle old refs for unknown ... - Jiralite
[discordjs/discord.js] New branch created: ci/docs-old-path
Should allow the workflow to run on old refs where newer packages are not in.
[discordjs/discord.js] New branch created: fix/add-text-displays-in-modals-lol
a78dd01 feat(guild): Support incident actions (#11131) - Jiralite
aac247c feat: add {add,remove}GroupDMRecipient methods... - almeidx [fcf7f27](https://github.com/discordjs/discord.js/commit/fcf7f27fd78b6de9b67c3758899e0abfab3af774) ci(release): handling for create-discord-app (#... - didinele [0c2975e](https://github.com/discordjs/discord.js/commit/0c2975e3fdc0513d2962a104d11092409dde8fdb) ci: implement workflow to publish dev versions ... - didinele [230e746`](https://github.com/discordjs/discord.js/commit/230e746b3165e320754ff947f4e02a3139668b0e) ci(documentation): Skip unknown packages on old... - Jiralite
a97ac82 fix(guide): Miscellaneous fixes (#11147) - Jiralite
[discordjs/discord.js] New branch created: feat/application-structures
[discordjs/discord.js] New branch created: fix/modal-resolving
8a9b331 ci: remove documentation workflow - Jiralite
Please describe the changes this PR makes and why it should be merged:
As of #11125 we no longer have a need or use for this workflow. The new workflow can and should be used for all releases now.
Status and versioning classification:
one of your commands exports no object with a .data key where this code loading and running it expects one
[discordjs/discord.js] New branch created: guide/missingaccess
[discordjs/discord.js] New branch created: guide/pageorder
Can't we use a static badge with the vanity invite instead of removing the discord invite fully?
That could work. Just dropping the link here: https://shields.io/badges/static-badge
We could keep both badges this way!
[discordjs/discord.js] New branch created: guide/headings
b80dd8c types(ClientEventTypes): fix messageDeleteBulk... - Pavel-Boyazov [f109fc9](https://github.com/discordjs/discord.js/commit/f109fc9b428999c0b3254838d68bd7468c8988fa) chore(guide): Update name of legacy path (#11149) - Jiralite [7de5b4a](https://github.com/discordjs/discord.js/commit/7de5b4a349d1769261d6ec41ccac8400b0ecf17d) refactor: remove guide route prefix (#11146) - almeidx [f1087c7](https://github.com/discordjs/discord.js/commit/f1087c7e8717c2b77444eeced07800151a760d6a) fix: Guide content path for CODEOWNERS (#11148) - Jiralite [af923fe`](https://github.com/discordjs/discord.js/commit/af923fee8e71b5f515478db070cbf53c3850ab1c) fix(WebSocketShard): bad error re-throw (#11151) - didinele
f9ca29e chore: update readme badges (#11152) - didinele
In this workflow run:
https://github.com/discordjs/discord.js/actions/runs/18362429706/job/52308581562#step:9:515
It says all those packages were released, but in actual fact, only discord.js was released. This is easily misinterpreted.
A possible remediation could be 2 arrays in the final output of released packages and packages that were not released (but were expected to).
Please describe the changes this PR makes and why it should be merged:
Fixes #11176
Status and versioning classification:
Please describe the changes this PR makes and why it should be merged:
Required for #11108 #11114
Build for builders is failing, it should be resolved in #11108
Status and versioning classification:
1a305fe build: bump discord-api-types to 0.38.30 (#11178) - imnaiyar
847fa99 fix(GuildChannel): manageable perm check (#11166) - didinele
dd79525 refactor!: remove special cases for bot guild o... - almeidx
180dd60 feat(voice): Add info about DAVE protocol depen... - jNullj
f9ca29e chore: update readme badges (#11152) - didinele
a2d4f18 chore(guide): consistent sidebar capitalization... - almostSouji
[discordjs/discord.js] New branch created: chore/bump-deps
- eslint-config-neon patch no longer needed
tseslint.config()->defineConfig(): https://typescript-eslint.io/packages/typescript-eslint/#config-deprecated
<img width="2412" height="1328" alt="Google Chrome Beta - 2025-10-18 at 11-37-02-UTC@2x" src="https://github.com/user-attachments/assets/85cb0cb6-f8d4-420d-915e-4fab82ac3179" />
Considering these docs aren't even shown in new docs site this should probably be rewritten. Same for the other case you disabled this rule.
[discordjs/discord.js] New branch created: fix/update-pinnable-migrated
This piece of code should be removed
https://github.com/discordjs/discord.js/blob/68835b3ff77e2cfe7776da8787f07b0abf02005c/packages/discord.js/src/structures/GuildChannel.js#L132-L142
If the permissions overwrites is empty, it does not mean that the permissions are synchronized
I realized what this piece of code is for, but it's wrong
Now I'll write how to reproduce the problem
I think I fundamentally disagree with this rule for many of the cases it changes here, especially when combined with padding-line-between-statements enabled for after multline blocks.
A couple of the changes made I do like (I never noticed them and it indeed makes it more readable).
The majority change 2+ lines of consecutive short-circuiting into exponentially more lines which makes it really hard to tell what is going on (every line becomes 4 with no easily readable and clear separati...
25b22c6 fix(ModalSubmitInteraction): Resolve components... - Jiralite
d03eb5e chore(guide): manually sort popular topics (#11... - almostSouji
0cc92bd fix(textInput): Allow empty strings for a value... - Jiralite
68835b3 refactor(guide): redirect old urls to /legacy (... - imnaiyar
697556f feat(website): parse and show unstable tsdoc ta... - Qjuh
63b5923 fix: Singular misplaced comma (#11194) - thelegendfox
c840249 feat: File upload support (#11108) - Jiralite
83ec0fd refactor: Use idPredicate for file uploads (#... - Jiralite
c9a9b6c feat: file upload component (#11114) - imnaiyar
f88b7b0 Merge branch 'main' into fix/404-no-package - kodiakhq[bot]
fcf7f27 ci(release): handling for create-discord-app (#... - didinele
0c2975e ci: implement workflow to publish dev versions ... - didinele
230e746 ci(documentation): Skip unknown packages on old... - Jiralite
7f29356 fix: ending uncached polls (#11157) - almeidx
a97ac82 fix(guide): Miscellaneous fixes (#11147) - Jiralite
[discordjs/discord.js] New branch created: feat/cda-release
[discordjs/discord.js] New tag created: [email protected]
[discordjs/discord.js] New branch created: feat/annotate
- Using
notice()for annotation - Handles case of no released or skipped packages (https://github.com/discordjs/discord.js/actions/runs/18788259066/job/53611961500#step:10:279)
5ccc6fe ci(documentation): ignore create* - Jiralite
[discordjs/discord.js] New branch created: ci/ignore-cdab
Path filters are not evaluated for pushes of tags.
[discordjs/discord.js] New branch created: fix/update-pinnable-use-pin-messages
[discordjs/discord.js] New branch created: fix/defunct-docs-logic
262a33a refactor(website,guide): cloudflare workers sup... - iCrawl
[discordjs/discord.js] New branch created: refactor/cloudflare
If we're doing this we should probably just...do job summary
[discordjs/discord.js] New branch created: fix/file-upload-fields
[discordjs/discord.js] New branch created: fix/file-upload-fields-main
As seen here:
There is a duplicate "guild" word. It should not be there!
[discordjs/discord.js] Pull request opened: #11212 [WIP] Fix duplicate 'guild' word in documentation
Thanks for assigning this issue to me. I'm starting to work on it and will keep this PR's description up to date as I form a plan and make progress.
Original prompt
This section details on the original issue you should resolve
Duplicate "guild" word in guild member flags bit field documentation
As seen here:
...
[discordjs/discord.js] New branch created: fix/check-if-in-voice-based-channel
ee3be2c refactor(ApplicationCommand)!: make options nul... - ckohen
756eac6 fix: Use D1 for indices (#11199) - Jiralite
08b87d9 refactor(website,guide): cloudflare workers sup... - iCrawl
633d481 fix: Remove outdated documentation logic (#11203) - Jiralite
2a5d99f ci(documentation): Ignore tag pushes for create... - Jiralite
c4a87b9 chore: fix executable file permissions - almeidx
[discordjs/discord.js] New branch created: chore/fixes
868be4e feat: Annotate result of releasing packages (#1... - Jiralite
[discordjs/discord.js] New branch created: fix/retry-google-fonts-fetch
4f9475d chore: fix executable file permissions (#11216) - almeidx
[discordjs/discord.js] New branch created: chore/readme-package-list
5f45492 chore: update readme package list - almeidx
Added missing create-discord-bot package, and added a new section for containers.
Alphabetically sorted the list (apart from discord.js itself)
Please describe the changes this PR makes and why it should be merged:
Makes it so that the term discordjs isn't censored in CI output
Status and versioning classification:
Hello everyone
Iโm trying to determine how many Server Boosts a specific user has contributed to a guild (for example: user A has contributed 2 boosts, user B has contributed 1, etc.). I want to use this to give different perks for single-boosters vs multi-boosters.
What I want:
- For a given user ID and guild, return their boost count (0, 1, 2, 3, ...).
What I already know / tried:
guild.premiumSubscriptionCountgives the total number of boosts in the guild (aggregate), ...
Specific questions for the community / maintainers
1.Is there any endpoint, field, or undocumented method that exposes a per-user boost count for a guild that I might have missed?
2.If not, what are recommended best practices for building a resilient multi-boost tracker? Are there hybrid approaches (gateway events + audit logs + polling) that actually work well in production?
3.Are there known edge-case patterns to watch for (gift boosts, refunded boosts, bot accounts, multiple boost...
What Iโd accept as answers
โNo โ the API does not provide this; track it yourselfโ โ include a recommended event flow and how to handle multi-boost decrements.
โYes โ hereโs the endpoint/field and an exampleโ (if one exists).
โUse audit logs + guildMemberUpdate and note these caveatsโ (detailed explanation appreciated).
Seeing as the original issue (#727) was closed over a year ago (with no real conclusion to the issue), and unit testing is still a hassle to implement, I'm opening this issue.
Describe the ideal solution
The ideal solution would be for snippets like the one below to simply work:
import {Guild, TextChannel, Message} from 'discord.js'; import {MockClient} from 'discord.js/mock'; const client = new MockClient(); const guild = new Guild(client, {}); ...
In this particular case I'd actually propose a breaking change to make it a Map/Collection. But guess for the purpose of this PR disabling the lint rule and a todo comment suffice.
756eac6 fix: Use D1 for indices (#11199) - Jiralite
08b87d9 refactor(website,guide): cloudflare workers sup... - iCrawl
633d481 fix: Remove outdated documentation logic (#11203) - Jiralite
2a5d99f ci(documentation): Ignore tag pushes for create... - Jiralite
3048c3c types(FileUploadComponentData): required shou... - Jiralite
Supersedes #11185 as Vercel doesn't want to build the guide on that branch
- eslint-config-neon patch no longer needed
tseslint.config()->defineConfig(): https://typescript-eslint.io/packages/typescript-eslint/#config-deprecated- removed explicit
reactStrictMode: truefrom nextjs configs as that is the default value
4c0d667 fix: retry google fonts fetch on fail (#11217) - almeidx
94a9b4d fix(Message): update pinnable to use PinMess... - sdanialraza [178c9cb](https://github.com/discordjs/discord.js/commit/178c9cb3483c74b16f1d0702522a73d87e6e89fb) fix(GuildMember): joinedAt possibly being NaN (... - TAEMBO [fb5c629](https://github.com/discordjs/discord.js/commit/fb5c62963833e693205212ad999e1613cdb599ad) chore: bump dependencies (#11225) - almeidx [9f64f4a`](https://github.com/discordjs/discord.js/commit/9f64f4aec79c34e0c890f4ddfa2ed1e2d77860ff) Merge branch 'main' into chore/readme-package-list - kodiakhq[bot]
d8b9134 ci: refactor turbo team to use var (#11219) - ckohen
d06d8c0 chore: update readme package list (#11218) - almeidx
[discordjs/discord.js] New branch created: fix/only-pass-relevant-options-fetching
Please describe the changes this PR makes and why it should be merged:
Status and versioning classification:
Please describe the changes this PR makes and why it should be merged:
Status and versioning classification:
Which application is this bug report for?
Documentation
Issue description
There's a bit of a discrepancy between the FAQ guides and the documentation and would love some clarification. I'm just confused as to where these get methods are being defined for roles, as the docs use fetch requests instead.
I see that interaction.options is defined by BaseInteraction. In the common use case of adding roles based on reactions, I don't think this works and you would need to use the `R...
getMember / getRole are convenience functions we define for interactions that let you retrieve the command options the user supplied (that being a member and a role in this example).
the guild member instance (retrieved via getMember or from the cache/rest call with .members.fetch("id")) then has the .roles.add() function on the guild member roles manager, to actually add a role.
if you...
[discordjs/discord.js] New branch created: chore/migrate-eslint-configs
that being said, i also want to bring attention to using buttons or select menus (or even relying on the discord-native onboarding feature).
"reaction roles" as a concept stems from a time where we had no better way of handling this.
reactions were never be meant to act as glorified buttons, and now we have proper buttons at our disposal!
ref: https://discordjs.guide/legacy/interactive-components/buttons
[discordjs/discord.js] New branch created: feat/deprecate-all-tag
78acab9 feat(ci): deprecate tag - didinele
@favna if you can take a looksy
[discordjs/discord.js] New branch created: refactor/take-ref
b90b33e refactor(publish-dev): take ref instead - didinele
06a75e8 docs: clarify wording for maximum values (#11231) - imnaiyar
Node v24 (LTS now) and setup-node@v6 please
[discordjs/discord.js] New branch created: chore/upgrade-setup-node
f5f48e9 chore: upgrade actions/setup-node to v6 and nod... - almeidx
Might be useful to include examples here
Thought:
- - name: Install Node.js v22
+ - name: Install Node.js
It's alright regardless.
Please describe the changes this PR makes and why it should be merged:
Semver is kinda annoying for non-pinned versions of prereleases....so we pin
Status and versioning classification:
i guess i am not such an active user where i'm in servers that are actively using buttons, but i will definitely take a look at this. thank you very much for the clarification & help :)
Your and scripts rely on , but you've listed it as a dev dependency. Did you think nobody would notice? This will crash in any environment that doesn't install dev dependencies. It's a rookie mistake. Maybe if you spent less time eating KFC and more time understanding how dependencies work, your scripts wouldn't be so fragile.\n\nlinted by bot
The and scripts in depend on , which is currently listed as a . This causes the scripts to fail in environments where only production dependencies are installed, such as in a CI/CD pipeline. Moving this package to would resolve the issue and ensure the scripts are runnable in all environments.\n\nsubmitted by bot
Please describe the changes this PR makes and why it should be merged:
nobody saw anything....
Status and versioning classification:
[discordjs/discord.js] New branch created: fix/og-image
These were pointing to a non-existent URL. The correct URL would have been https://discord.js.org/open-graph.png.
However, both sites have a custom opengraph image which overrides this setting anyways.
Left the open-graph.png image in the public folders regardless since it might be used somewhere this repository(?)
4359914 fix: open graph image in metadata (#11244) - almeidx
The short answer is: No.
You can technically configure boost messages in a server and listen for them - they are authored by the boosting member - but you won't get notified of people dropping boosts as long as they still have one (premiumSince will persist)
<img width="405" height="179" alt="image" src="https://github.com/user-attachments/assets/1463ca87-7a5d-4937-aeec-0415e4c70e51" />
i diffed these two boost messages and they are identical save the timestamp, message id, so no way t...
178c9cb fix(GuildMember): joinedAt possibly being NaN (... - TAEMBO
fb5c629 chore: bump dependencies (#11225) - almeidx
d8b9134 ci: refactor turbo team to use var (#11219) - ckohen
d06d8c0 chore: update readme package list (#11218) - almeidx
f26a5ed fix: only pass relevant options to API when fet... - sdanialraza
- No
- Not doing that, honestly
- All of the above
- None that I am aware of, that'd be a question/suggestion for https://github.com/discord/discord-api-docs
Configure your app to be available as user install via contexts in the app portal: https://discord.com/developers/docs/resources/application#setting-supported-installation-contexts and add it via the link in its profile (which is what that configures)
<img width="1747" height="967" alt="image" src="https://github.com/user-attachments/assets/e9fa9db2-46d8-4403-8ae2-3b073f701c96" />
alternatively, you can compose the link yourself: https://discord.com/developers/docs/topics/oauth2#authori...
Side note: you can have Discord validate user IDs natively, if you use a "user" command option instead of a string! More on that: https://discordjs.guide/legacy/slash-commands/advanced-creation#option-types
[discordjs/discord.js] New branch created: ci/deprecate-comment-fix
Removing this allowed the workflow to run properly.
Tested: https://github.com/discordjs/discord.js/actions/runs/19101585322
[discordjs/discord.js] New branch created: feat/builders-file-output
7bb703f feat(builders): multipart form data output support - didinele
WIP. blocked by some REST changes I'll be making in another PR
Regardless, the proposed API can be reviewed already
[discordjs/discord.js] New branch created: fix/builders-typo
[discordjs/discord.js] New branch created: fix/data-removal